Hello,

I'm wondering which control panel would perform better with a Virtuozzo VPS; Plesk or cPanel?

With which I should expect a better performance?

It's for my personal use so I don't care about features, and what people love.

I believe Plesk is better since it's from Virtuozzo company!

As long as you have 256mb of ram, cpanel and plesk will perform the same.

I use plesk for all of my personal "play accounts" but that's just a personal preference for me.

Even if you have 256, I would still say Plesk. 256 is the bare minumum cPanel will really run. Plesk requires much less, as a result of its much smaller memory footprint.

Plesk all the way. (plus it's nicer too)

Based on the fact that the Plesk Virtuozzo templates are optimized for Virtuozzo and are in fact templates rather than full installs of the control panel, Plesk should in theory run faster than cPanel since cPanel does not run from a template in Virtuozzo and must be installed just like it would be on a dedicated server. Plesk installed into a Virtuozzo VPS will make use of the hardware node template and thus use fewer resources. Of course I have no actual benchmarks to confirm this, I'm simply speaking in theory based on the architecture of Virtuozzo and Plesk.

This being said, both can perform very well in a Virtuozzo VPS and the decision largely comes down to personal preference. My advice is Plesk simply because I have had great success with it and I prefer the "stable" nature of the Plesk control panel vs. the frequently updated and more "bleeding edge" approach that cPanel takes. Yes you can opt for the stable version of cPanel but I still don't feel it's as solid as Plesk when it comes to stability.

Good luck with your choice!

Based on the fact that the Plesk Virtuozzo templates are optimized for Virtuozzo and are in fact templates rather than full installs of the control panel, Plesk should in theory run faster than cPanel since cPanel does not run from a template in Virtuozzo and must be installed just like it would be on a dedicated server. Plesk installed into a Virtuozzo VPS will make use of the hardware node template and thus use fewer resources. Of course I have no actual benchmarks to confirm this, I'm simply speaking in theory based on the architecture of Virtuozzo and Plesk.

This being said, both can perform very well in a Virtuozzo VPS and the decision largely comes down to personal preference. My advice is Plesk simply because I have had great success with it and I prefer the "stable" nature of the Plesk control panel vs. the frequently updated and more "bleeding edge" approach that cPanel takes. Yes you can opt for the stable version of cPanel but I still don't feel it's as solid as Plesk when it comes to stability.

Good luck with your choice!

I agree, Plesk is far superior when your using it in combination with Virtuozzo. Besides the fact that it runs off a root template on the host node, the memory footprint is indeed HALF as much as what cPanel takes up. Even the number of processes running in a Plesk VPS versus a cPanel VPS is half as much.

-Sean

sorry to slightly hijack your thread, but my question is along the same lines:

what if I were running 384 mb of ram and also icecast server. which would be better, plesk or cpanel? anyone know if icecast will integrate with either control panel better or be completely incompatible? I have expirience with cpanel but the online demos of plesk are very enticing, which is better feature wise?

I agree, Plesk is far superior when your using it in combination with Virtuozzo. Besides the fact that it runs off a root template on the host node, the memory footprint is indeed HALF as much as what cPanel takes up. Even the number of processes running in a Plesk VPS versus a cPanel VPS is half as much.

-Sean

PLease verify your statements before you make such pronouncements. The virtuozzo application templates can save you the code part per each vps. Now we have a full hosting platform that uses 9MB RSS. That's code + stack + heap. So the code part would be around 4-5MB or less, and that is the amount of memory you can save using virtuozzo application templates. Making statements like 'Application templates can save HALF the memory' just show complete lack of understanding of how an application template actually works.

Thanks.

yeah plesk have a great features too i know cpanel is the most used one but plesk is the most great one ;)

PLease verify your statements before you make such pronouncements. The virtuozzo application templates can save you the code part per each vps. Now we have a full hosting platform that uses 9MB RSS. That's code + stack + heap. So the code part would be around 4-5MB or less, and that is the amount of memory you can save using virtuozzo application templates. Making statements like 'Application templates can save HALF the memory' just show complete lack of understanding of how an application template actually works.

Thanks.

If you read my post carefully, you will see that I said:

"Besides the fact that it runs off a root template on the host node, the memory footprint is indeed HALF as much as what cPanel takes up."

I was saying the memory footprint is HALF as much as cPanel. The application templates play no part really in memory consumption, they simply provide a tighter disk space allocation versus cPanels full file size installation on a VPS.

The only place I see 'Application templates can save HALF the memory' is in your post.

-Sean

If you read my post carefully, you will see that I said:

"Besides the fact that it runs off a root template on the host node, the memory footprint is indeed HALF as much as what cPanel takes up."

The only place I see 'Application templates can save HALF the memory' is in your post.

-Sean

Considering that plesk and cpanel actually runs the same set of applications (apache, mailman, spamassassin, Bind. For idle usage, I think exim and qmail has near same memory requirement.), I am really surprised how plesk can run on half the memory. Cpanel does have some extra daemons running, but they all have around 900KB RSS, from what I saw. Plesk runs apache+mod_php as their own backend and the main server too, and overall plesk will have higher memory usage at moderate to high loads, as compared to Cpanel which uses Suexec to run php. Running pre-fork with mod_php is the worst way to run apache--at least from a memory perspective.

So under normal circumstances, Plesk will end up taking much higher memory--at moderate to high loads. (since they are running mod_php). So only miraculous application templates can reduce the memory footprint it to half the cpanel usage.

I was speaking in terms of usability and real world use. How much can you really do on a cPanel VPS with 256MB of guaranteed RAM? Much less than you can do with a Plesk VPS under Virtuozzo with the same amount of memory.

I'm not talking about exact memory footprints down to the kilobyte, thats the viewpoint of a developer and therefore I have no business in commenting about how much memory each individual component takes up in stack, heap, et. al. My comments are based on real world experience from actually hosting different types of VPS's and control panels in a production environment and interfacing with clients that use both control panels.

-Sean

I was speaking in terms of usability and real world use. How much can you really do on a cPanel VPS with 256MB of guaranteed RAM? Much less than you can do with a Plesk VPS under Virtuozzo with the same amount of memory.

I'm not talking about exact memory footprints down to the kilobyte, thats the viewpoint of a developer and therefore I have no business in commenting about how much memory each individual component takes up in stack, heap, et. al. My comments are based on real world experience from actually hosting different types of VPS's and control panels in a production environment and interfacing with clients that use both control panels.

-Sean

I have been obsessing about memory usage for the last week, trying to create the perfect hosting platform for vpses, and they are just my observations :-). As such, CPs are irrelevant when it comes to system load (memory/cpu), and I think this is a sentiment expressed by someone who has real world experience too (twhiting in a thread about cpanel vs directadmin). The load is determined by the main services, apache/bind/spamasassin/proftpd. Anyway, it is possible you are more comfortable with tuning Plesk than Cpanel, and can get Plesk to run comfortably at lower memory. Theoretically, Plesk is supposed to have higher memory usage, owing to mod_php and proftpd, than cpanel. Maybe you should ask Swsoft to enable SuPhp Support, which can actually save a lot of memory. Swsoft seems to be lopsided company, with all the innovations made by the virtuozzo team--like application templates--nullified by the bad design on the part of plesk. :-)

Thanks.

I use cPanel, but i have heard that plesk is extreamly good!

We've recently started shipping servers using Virtuozzo and Plesk and from the customers we've sold to so far - the feedback has been great.

Theres no doubt cPanel is a great bit of kit but I know where my own personal preference lays.

Hello,

This thread inspired me to start a thread on our forums, comparing the control panel memory usage.

To be brief, Plesk did use quite a bit less RAM than cPanel. DirectAdmin used even less than Plesk.

Of course, this is hardly definitive evidence and I'm sure there are quite a few different things to be considered, it was certainly interesting though.

John,
Are you willing to share any hard stats/figures on your findings?

Thanks.

Hi,

I don't want to get into trouble with the mods, but I did start a thread about this on our own forums.

Feel free to check it there.

Hi,

I don't want to get into trouble with the mods, but I did start a thread about this on our own forums.

Feel free to check it there.

I don't understand your problem. You needn't post a link to your forum, instead you can directly post your findings here. I am sure the mods would be more than happy to see someone posting useful information on their forums.

I am again surprised. DA uses less memory primarily because they use majordomo instead of mailman. I am sure your configuration of cpanel had mailman, but not plesk. also Check you have all the services--including spam turned on for all the three. DA disables spamassassin by default, so check that too.

thanks.

Hi,

I don't want to get into trouble with the mods, but I did start a thread about this on our own forums.

Feel free to check it there.

For the mod_php effect to kick in, run apache benchmark suit and load your webserver for a couple of minutes and leave it and measure the memory usage again. You will see how terrible mod_php is vis-a-vis memory usage.

Thanks.

Hi,

Ok, here we go.

We have created three new VPS and have installed DirectAdmin on the first, Plesk on the second and cPanel on the third. We will then look at the memory usage of a new VPS freshly installed with each control panel.

The DirectAdmin system was the first to be installed. Immediately after the DirectAdmin install had finished we checked the memory usage.

The usage was at 127 MB. Please note, this is just with the control panel running and with no websites setup within.

We then setup a new VPS to use for Plesk. After the install we checked the memory usage.

The usage was at 194 MB. Please note, this is just with the control panel running and with no websites setup within.

Finally we installed another VPS to test cPanel on. After the install we checked the memory usage.

The usage was at 286 MB. Please note, this is just with the control panel running and with no websites setup within.

Surprised with the results? I must admit I was too.

So I did a further test. I restarted each VPS and waited for 5 minutes. I then checked the memory usage again.

DirectAdmin was at 124 MB, almost the same usage.

cPanel was at 222 MB, quite a big difference there.

Plesk was at 161 MB, less than before.

Hi,

Also, yes, there are ways to save memory with cPanel. These were all just default installs.

Also, I should point out, the Plesk install was via a template.

Hi,


We then setup a new VPS to use for Plesk. After the install we checked the memory usage.

The usage was at 194 MB. Please note, this is just with the control panel running and with no websites setup within.

Finally we installed another VPS to test cPanel on. After the install we checked the memory usage.

The usage was at 286 MB. Please note, this is just with the control panel running and with no websites setup within.

Surprised with the results? I must admit I was too.

So I did a further test. I restarted each VPS and waited for 5 minutes. I then checked the memory usage again.

DirectAdmin was at 124 MB, almost the same usage.

cPanel was at 222 MB, quite a big difference there.

Plesk was at 161 MB, less than before.

Can you tell me if all the three had all the services enabled? Did plesk have mailman on? Spamassassin? What about DA?

A [ ps ax ] for each vps would be great.

Thanks.

this has been talked too many times under different topics and my vote goes for cPanel..

Can you tell me if all the three had all the services enabled? Did plesk have mailman on? Spamassassin? What about DA?

A [ ps ax ] for each vps would be great.

Thanks.

Hi,

If you want the login details for each of the VPS, let me know. I can see this thread going on for quite awhile and to be honest, my working day is now over :)

Hi,

If you want the login details for each of the VPS, let me know. I can see this thread going on for quite awhile and to be honest, my working day is now over :)

Yeah, that would be great. I just need to know if you can make an apples to apples comparison of cpanel vs plesk vs DA. You can PM me here.

Thanks.

Yeah, that would be great. I just need to know if you can make an apples to apples comparison of cpanel vs plesk vs DA. You can PM me here.

Thanks.

OK,

Thanks John for sending me the vps information so I could look inside. Here's a very quick review:

Cpanel had both spamassassin and mailman turned on. Plesk had both turned off. In other words, plesk system didn't have either mailing list or spam blocker. Though in a bad design on the part of cpanel folks, they have integrated the spamassassin-init script into exim, and the mailman-init script into cpanel itself, so there is no way you can turn off mailman and spamd alone on cpanel. In any case, plesk is lacking two pivotal services, both of which takes up heavy memory.

If you have a plesk template that has both spamd and mailman, and then compare, you will be able make a better judgement. As such, I am not a cpanel expert, so I wasn't able to shut down spamassassin and mailman alone. I am sure there is some method to do that via the CP.

The verdict is: Plesk will use equal (or even more) memory compared to Cpanel, if they have the same set of services.


Thanks again John.

OK,

Thanks John for sending me the vps information so I could look inside. Here's a very quick review:

Cpanel had both spamassassin and mailman turned on. Plesk had both turned off. In other words, plesk system didn't have either mailing list or spam blocker. Though in a bad design on the part of cpanel folks, they have integrated the spamassassin-init script into exim, and the mailman-init script into cpanel itself, so there is no way you can turn off mailman and spamd alone on cpanel. In any case, plesk is lacking two pivotal services, both of which takes up heavy memory.

If you have a plesk template that has both spamd and mailman, and then compare, you will be able make a better judgement. As such, I am not a cpanel expert, so I wasn't able to shut down spamassassin and mailman alone. I am sure there is some method to do that via the CP.

The verdict is: Plesk will use equal (or even more) memory compared to Cpanel, if they have the same set of services.


Thanks again John.


Hi,

Just before I leave. It was fine until your last paragraph. You just said you couldn't compare it and then proceeded to make a guess....

My verdict, this argument can't be won :) Use whatever control panel you like best.

Hi,

Just before I leave. It was fine until your last paragraph. You just said you couldn't compare it and then proceeded to make a guess....

My verdict, this argument can't be won :) Use whatever control panel you like best.

I am primary a theoretical person, and naturally made that assumption because of plesk's mod_php, which can wreak havoc at high loads.

The ideal is lighttpd + fastcgi. You can scale to 8.64 million (*) hits per day on 100MB ram. I am sure at such loads, cpanel/plesk machines would implode into themselves creating a blackhole.


* Assuming each php process to 0.1 seconds to complete, and you have 10 php_fcgi processes, you can have 100 connects per second, and that would 86400 * 100 hits per day or 8.64 million hits per day. 10 php_fcgi processes would take around 7-10MB each leading to 70-100MB ram usage.

Thanks.

Being somewhat of a noobie, I was a bit disappointed by whm/cpanel. Bugs like parking a domain on top of another and loosing the assigned ownership information (and yes, I know how to google, there are answers how to fix the unpark error) were a bit irritating. After an "emergency" move to another provider that we have good trust in - to some extent based on the opinions voiced in this forum - I currently get used to Plesk. Naturally it has a learning curve, just like anything else, but while I have a sense of reality with regard to bugs, at least so far it's been good to me getting simple processes done.

...I'm wondering which control panel would perform better with a Virtuozzo VPS; Plesk or cPanel? With which I should expect a better performance?

Cpanel is a nice control panel but it has frequent problems when you update it, all kinds of things seem to break every update, even using the stable or release versions. My advice is to keep updates to a minimum if possible. As a server admin I would want cPanel, but the panel is not for you but for your clients, they need an easy to use interface, Plesk has been able to provide such interface and the main reason many hosts end up using it, another reason is that you would like to have a panel for both Windows and Linux/Unix servers, Plesk allows you to manage many servers at same time, to me Plesk is the way to go.

Personally I prefer Plesk over cPanel simply because of the software version(s) of apache/mysql/php and the lower resource intensive nature.I'm not sure how Plesk is for buggy updates for their software, I'd really like to get a Plesk box and see how it performs. I've used both with different companies I manage - I'd recommend Plesk definItely. cPanel is more idiot-friendly (if you don't have some of those yet, you'll get some ) but Plesk is a much, much more stable platform. If you want to 'sell' hosting, cpanel is your best bet due to the features. Plesk is less resource intensive, more secure (better, up to date software) - and generally 'simpler' for the basic things, but cpanel wins with more features and simpler access to all those extra features that web hosting providers usualy need for their clients. Note: Is It Possible To Run Plesk & cPanel on the same server. I would like to have both on the same server or will there be problems. Im not trying to have the same accounts under each but let customers choose at sign up which, control panel they would like. cPanel and Plesk operate on different ports already. I think it should be ok but, I would hate to have to reinstall a server with a bunch of clients on it.

If your next level from reseller is VPS or dedicated you have to choose between cPanel and Plesk (the leaders) and DirectAdmin, Ensim, Webmin and more. But these control panel are only an interface to turn easy a server accounts administration and more. If you really know what you are doing the best control panel is the command line...Per example: if you are using a Plesk for 10 domains only you can start a Linux shell and setup 100 domains or 1,000 domains hosted in your server. Obviously, only 10 will have control panel. Well, control panel is essential for your customers...The great advantage of control panels really improved is provide you the ability to migrate easy and quickly from one server to another preserving all setups in all accounts. On this issue I strongly recommend Plesk because it is the best in show in migration, but note that Plesk 7.5.1 Reloaded cannot migrate data from the new Plesk 8.0.1...Plesk Migration Manager migrates fine from cPanel reseller account (if your reseller hosting gives you a sudo...) and all setup will be migrated fine, including all email accounts, forums and more! But cPanel at this time cannot migrate accounts from Plesk 7.5.4. and 8.0.1. yet, only from old Plesk versions as releases 6x. A new cPanel capable to migrate from recente Plesk releases is in development and coming soon.

We recently migrate a lot of gigas from Washington to Texas at 252kbps in media using Plesk 8.0.1. and migrated fine from Houston to Dallas between 512/650kbps in media without only one error!! We are specialized in host for VIP and intellectuals and we own various VPS and dedicated around the world; constantly we are migrating fine and we migrate using Plesk only. Our most recently migration has been performed by Zone.Net Sean Koons from The Planet (Plesk 8.0.1) to SoftLayer (Plesk 8.1) and this new environment is running just fine. With Plesk you will be free for migrations but you will be a Plesk slave for life...

Cpanel is a nice control panel but it has frequent problems when you update it, all kinds of things seem to break every update, even using the stable or release versions. My advice is to keep updates to a minimum if possible. As a server admin I would want cPanel, but the panel is not for you but for your clients, they need an easy to use interface, Plesk has been able to provide such interface and the main reason many hosts end up using it, another reason is that you would like to have a panel for both Windows and Linux/Unix servers, Plesk allows you to manage many servers at same time, to me Plesk is the way to go.

Some principal advantages of Plesk (most recent releases - 8x)are as follows:


1. Multiple Remote Databases support - Plesk 8 allows you to use remote database servers for storing client databases. Moreover, you can easily employ and manage multiple external MySQL and PostgreSQL database servers at once.

2. Improved databases administration - This release offers extended database administration capabilities and improved PhpMyAdmin and PhpPgAdmin integration. Plesk server administrators now have the full-fledged database administration ability via phpMyAdmin and PhpPgAdmin, being able to create database users, manage their access rights and remove users, if necessary. Improved database administration capabilities now allow you to choose the default user for DB WebAdmin feature.

3. Simultaneous migration support - Plesk Migration Manager now allows simultaneous (a.k.a. multisession) migrations. This new feature is a definite time-saver, especially for Expand migrations. Simultaneous migration is easy and convenient way to migrate data from several servers at once.

4. Simplified IP mapping during migration - Simplification of IP mapping in Plesk Migration Manager makes migration even quicker and easier than it was before. All excessive IP mapping is removed, as you only need to map those IPs that are actually used by migration objects. Site Applications and Application Vaults migration - the ability to migrate Site Applications and Application Vault is a great new functionality for Plesk Migration Manager. This feature is another big step towards perfect migration brought to you by Plesk team. PostgreSQL databases migration - Plesk Migration Manager now can migrate PostgreSQL databases from one Plesk server to another, further increasing the functionality and flexibility of migration.

5. Sender Policy Framework (SPF) support - Plesk 8 adds the support of popular and very effective SPF (Sender Policy Framework) spam prevention system. SPF is based on using special DNS records that specify which machines are authorized to transmit e-mail for a specific domain, thus making it easy to distinguish genuine e-mails from those forged by spammers. For more information about Sender Policy Framework system, refer to http://spf.pobox.com/howworks.html.

6. Pluggable Authentication Modules authentication support - In this release the support for Pluggable Authentication Modules (PAM) authentication was added. PAM authentication is flexible mechanism for authenticating system users, further improving Plesk server security. APOP authentication support - In this release encrypted APOP authentication for POP3 protocol is added. Your mailbox passwords will never be transmitted in plain text again - APOP is using MD5 hash, providing quality encryption and secure authentication of transmitted e-mail credentials.

7. Qmail Queue Management through Control Panel - This feature allows administrators to manage the Qmail message queue directly through Plesk Control Panel. With this feature, you can manually delete spam and other unwanted mail from the queue, using quick and intuitive sorting options.

8. PHP 4.4.2 upgrade for FreeBSD - FreeBSD versions of Plesk 8 come with PHP upgraded to 4.4.2 version. PHP 4.2.2 offers increased performance and security among other improvements.

9. Dr.Web 4.33 updated - Dr.Web anti-virus is upgraded to new 4.33 version in Plesk 8. Additionally, brand-new Plesk Autoinstaller V3 can successfully update all Dr.Web components, thus making previous Dr.Web autoupgrade problems obsolete.

10. SpamAssassin 3 upgrade for FreeBSD - FreeBSD versions of Plesk 8 come with SpamAssassin 3 included. This new SpamAssassin version further improves the quality of spam filtering, while fine-tuning SpamAssassin's already outstanding performance. Use of mod_jk module instead of mod_webapp module - Plesk 8 now uses mod_jk module instead of outdated mod_webapp module for its Java-related needs.

11. Improved support of Chroot Shell Environment - Plesk 8 vastly improves disk space usage for Chroot shell environment in vhost. Now disk space usage for chroot shell environment in vhost is minimized, saving your precious free HDD space.

12. Secure administrator password retrieval - This new feature allows Plesk server administrator to retrieve and change the administrator's password without logging in to Plesk and without compromising the Plesk server security.

13. Host name validation during install - Plesk 8 now validates the host name during the installation process, checking the compliance of host name with IP address. This eliminates several possible problems during the installation, improving Apache and MySQL operation consistency.

14. New informative welcome screen - When you log in to Plesk 8 for the first time, a welcome screen with short and to-the-point description of new features will be presented. This will help you familiarize yourself with plethora of new features available in Plesk 8.

15. Initial configuration improvement - Plesk 8 allows you to configure default IP addresses at the first startup, making the process of initial Plesk configuration quicker and easier. MD5 authentication in XML RPC - Plesk 8 gives you the option to use MD5 authentication in Plesk XML RPC. This vastly improves Plesk Control Panel security when using Plesk API, enabling you to encrypt the passwords and protect Plesk from potential hacker attacks.

16. Improved SpamAssassin and Dr.Web API management - With Plesk 8 you can manage SpamAssassin and Dr.Web through Plesk API much more effectively than before, utilizing a wide range of commands and options previously unavailable for API management.

17. CLI interface utilities update - Beginning with Plesk 8, CLI interface utilities do not use .sh name suffix anymore. We recommend all Plesk 8 users to use the new, more convenient syntax. While the old syntax will be supported for a while, it is outdated and its support will eventually cease.

18. Brand new context help files and user's guides - we have prepared brand new documentation set to help you satisfy your Web hosting management needs faster and easier. If you cannot find any information you need, or would like us to add more details on specific operations or give explanations of how something works, please let us know by dropping a letter to userdocs@swsoft.com: We want to help you and will try to add the information you need as soon as possible.

And more... much more...

Regards,

Plesk will use more memory than Cpanel owing to mod_php. The 'less resource' of plesk is basically outright fraud, and this is because it comes with two main services turned off: Mailman and spamassassin. Ultimately for moderate to high loads, plesk will need more memory, and even Swsoft recommends 512MB burst for plesk.

Contrast this with lighttpd based solution, that can run in 128MB burst.

Hi,

Also, yes, there are ways to save memory with cPanel. These were all just default installs.



This is exactly the thread/discussion I was looking for
(I know it's mentioned here and there but this is much more focused)

John could you please give some suggestions how to reduce the cpanel footprint?
Is there anything obvious and easy? Even "just" 64mb would be a nice drop.

(btw we happen to be a new customer of yours and rather pleased so far)

This is exactly the thread/discussion I was looking for
(I know it's mentioned here and there but this is much more focused)

John could you please give some suggestions how to reduce the cpanel footprint?
Is there anything obvious and easy? Even "just" 64mb would be a nice drop.

(btw we happen to be a new customer of yours and rather pleased so far)

Hi,

Please open a ticket with support and they will take care of it for you.

Ah, how embarrassing, I confused your company name with another...

Up way too many hours today with way too little sleep, sorry!

cPanel definately mate, I have been using cPanel for years and will carry on using it ;)

cPanel definately mate, I have been using cPanel for years and will carry on using it ;)Thanks for your contribution, as it's obvious you've never had any experience with Plesk.

Well I've come across it and it's horrible (In my opinion).Thanks for your contribution, as it's obvious you've never had any experience with Plesk.

Originally Posted by Connect-Hosting
cPanel definately mate, I have been using cPanel for years and will carry on using it
Thanks for your contribution, as it's obvious you've never had any experience with Plesk.

You are right. If anyone try Plesk for some time he will kick out cPanel. Well, cPanel is fine, but have a lot of problems and it is not stable like Plesk or Direct Admin. For us in a comparison between cPanel and Direct Admin we prefer Direct Admin.

Regards

You are right. If anyone try Plesk for some time he will kick out cPanel. Well, cPanel is fine, but have a lot of problems and it is not stable like Plesk or Direct Admin. For us in a comparison between cPanel and Direct Admin we prefer Direct Admin.You can't even compare cPanel to DirectAdmin; cPanel doesn't even come close.

You can't even compare cPanel to DirectAdmin; cPanel doesn't even come close.

Sorry, but we really can do this comparison and many others. We used cPanel since its first version. We used Plesk since it's first version and we used Direct Admin since it's first version. We recently found serious security holes in cPanel in a monster server we have and we replaced it by Direct Admin: no more problems we encountered. In another server we have we are using cPanel installed in one port and Plesk in another port; recently we tried install Direct Admin in a third port and we made a comparison. We are using control panels before the famous Feature Price disaster, in Fort Lauderdale, where we crashed in shared and entered the VPS market. We also ported some control panels to OS/2 Warp.

Regards

Sorry, but we really can do this comparison and many others. We used cPanel since its first version. We used Plesk since it's first version and we used Direct Admin since it's first version. We recently found serious security holes in cPanel in a monster server we have and we replaced it by Direct Admin: no more problems we encountered. In another server we have we are using cPanel installed in one port and Plesk in another port; recently we tried install Direct Admin in a third port and we made a comparison. We are using control panels before the famous Feature Price disaster, in Fort Lauderdale, where we crashed in shared and entered the VPS market. We also ported some control panels to OS/2 Warp.

RegardsI actually meant that in positive regards towards DirectAdmin. You're comparing two pieces of software, but one of them (DirectAdmin) is so much better.

I actually meant that in positive regards towards DirectAdmin. You're comparing two pieces of software, but one of them (DirectAdmin) is so much better.

Ah! We finally understand correctly your comment! We apologize, because we have not good English! Yes, Direct Admin is so much better, basically because simple is cool.

Cheers

The majority seem to use cPanel, but if I had it my way, Plesk would at least be the option, if not the cpanel used. I've only begun using Plesk in the last year and preferably suggest it over any other cpanel to date so far from my own experience with usage and what not.

The majority seem to use cPanel, but if I had it my way, Plesk would at least be the option, if not the cpanel used. I've only begun using Plesk in the last year and preferably suggest it over any other cpanel to date so far from my own experience with usage and what not.

Yeah, Plesk is the creme de la creme but also have some serious problems if you are using it from Virtuozzo templates:
1 - If a misconfiguration appears you cannot fix it easy and a lot of manual adjusts are wanted
2 - In 60% of snapshot tasks (entire VPS backup) directly from Plesk CP backup fails if the shared CPU resources are high loaded
3 - Webalizer fails and your statistics on traffic stops and if you face this problem, just SSH
to server and run this script /usr/local/psa/admin/sbin/statistics.
4 - Watchdog fails to correctly monitor httpd (Apache) if it is very unstable and a square golden icon replaces the normal round green one. In this case you have to set a cronjob to restart Apache minutely.
5 - When you migrates from a server to another using PMM snapshot and client and domains backups cannot be migrated, then you must have them in a external server.
6 - Due "normal" misconfiguration the embedded CP in Virtuzzo and vice-versa for login simply cannot be performed.
7 - If you forget your pswd this one cannot be retrieved by clicking the recover option.

If you rent a dedi and install Plesk by autoinstaller for shared web hosting purposes in this case you have not problems...

Regards