This is one of the most comprehensive threads I\’ve read since starting with Magento.
I haven\’t been involved with computer server stuff since back when WindowsNT emerged.. So I could use some recommendations..
I was using Volusion software, but for the $160/month for unlimited product hosting (have 10,000 + product store) and no real support for backend issues like pulling feeds from my distributors stock status, etc., I gave it up when I found Magento..
Where I need some advice is on choosing a new server.
I\’m currently on GoDaddy shared Linux hosting platform, 2.1 Config.
Would this be enough juice to run Magento proficently. And which CP would I really need since I\’m not familiar with the server software?
RAM:2 GB, Storage:30 GB, Bandwidth:1,000 GB,
Other control panels options include;
Simple Control Panel Unlimited: $0.00/mo
Parallels Plesk Panel 30 Domains: $4.99/mo
Parallels Plesk Panel 100 Domains: $6.99/mo
Parallels Plesk Panel Unlimited: $9.99/mo
Parallels Small Business Panel: $9.99/mo
cPanel Unlimited: $9.99/mo
You should probably consider a hosted Magento solution so that you don’t have to deal with things like backups, email servers, etc.. and have access to tech support with Magento experience. I can’t recommend one myself though. If you want a full DIY solution I recommend Linode. A 2Gb or 4Gb VPS running 64-bit Ubuntu 10.04 LTS is plenty powerful for most stores, especially if properly configured with nginx for static content, properly tuned MySQL, APC/memcached, etc.. However, this really isn’t for the faint of heart so if your experience is limited to WindowsNT days then you will either want to hire someone or plan on spending a lot of time getting setup and learning. IMO the control panels are nice for simple software packages, but to get a fast Magento installation you just need to manually configure it and the CPs just get in the way.
I was trying my host to install APC. They did, but after APC was installed, my site was not loading properly; it would load only some parts of a page but not completely. And every other time the site would produce 500 Server Error. So, I talked to my hosting support team (BlueHost.com, by the way) and it seemed as now one would care until I gave up and asked them to delete the whole APC thingy completely. I was super lucky that my message got to one smart guy at BlueHost support named Matt. And this is what Matt wrote to me
Most of tech supports won’t know that when you use APC, you cannot run Zend Optimizer in your site.
Also, To have APC work, you have to use FastCGI. Therefore, I have made two modifications to your account:
1) I have put your account on PHP5 (FastCGI)
All files with the extension .php will be handled by PHP5 FastCGI processes.
2) in your php.ini file, i have removed the zend optimizer line:
zend_extension=/usr/lib64/php/zend/ZendOptimizer-5.2.so
This allows your website to load using the APC module without seg-faulting and throwing a 500 error.
Your website is working at this time, can you please check your website?
Thank you,
Matt
Level II Tech Support Engineer
That fixed the all the trouble I had after installing APC. Today’s morning could not be better! My site is running super fast now!
Thanks Stuart, thanks to everyone who contributed to this forum, and thank you Matt from BlueHost.com.
I was trying my host to install APC. They did, but after APC was installed, my site was not loading properly; it would load only some parts of a page but not completely. And every other time the site would produce 500 Server Error. So, I talked to my hosting support team (BlueHost.com, by the way) and it seemed as now one would care until I gave up and asked them to delete the whole APC thingy completely. I was super lucky that my message got to one smart guy at BlueHost support named Matt. And this is what Matt wrote to me
Most of tech supports won’t know that when you use APC, you cannot run Zend Optimizer in your site.
There are some great tips on this thread for speeding up magento. Many of them apply to any website (like frontend css/js compression with gzip, etc...). Unfortunately, recommendations for magento can be all over the place sometimes. I guess that\’s what you get with a community.
At TinyBrick, we\’ve been working on enterprise-level magento implementations for a few years now, and I\’d say the biggest slowdown for folks is a basic understanding of the framework and what needs to load when. Which is one of the reasons we developed Lightspeed.
Lightspeed - A whole-page caching utility on par (and better in some ways) with the whole-page caching that comes stock in Magento Enterprise Edition.
While we definitely recommend all the front-end compression that this thread emphasizes, we feel that magento is inherently too big/heavy to run without caching. (That\’s why threads like this have done so well)
And when it comes to magento caching, LIghtspeed is the best. (Our customers agree)
Goto Magento Admin -> System -> Cache Management
- Tick the following items:
-- Configuration
-- Layouts
-- Block HTML output
-- Translations
-Untick the following items: (if ticked they seem to have a negative impact atm)
-- Collections Data
-- EAV types and attributes
-- Web Services Configuration
I found it the most beneficial for my ‘view all’ page which was slow as a dog due to the number of products being generated by the list.php block. you simply add this code to your list.php and it caches the block everytime a product is saved. The first time the page loads takes ages but after that it’s saved in the magento cache so it’s lightning quick. I brough my speeds down from over 10secs to load the page to one and a bit secs!
Goto Magento Admin -> System -> Cache Management
- Tick the following items:
-- Configuration
-- Layouts
-- Block HTML output
-- Translations
-Untick the following items: (if ticked they seem to have a negative impact atm)
-- Collections Data
-- EAV types and attributes
-- Web Services Configuration
And once you have your 9500+ product website up and running and optimized so it serves 1-2 second html loads on a dedicated 4 core server with 6GB ram, do yourself a favor and install Tiny Brick’s Light Speed Page Caching. Your website won’t fall flat on its face when an aggressive web spider like Baidu hits it.
After you’ve got a website up and running with Lightspeed page caching, such that it will keep up and running while simultaneously serving your customers, Google, Bing and Yahoo; then Baidu and Yandex will pay a visit and it once again falls flat on its face.
Next step, take a load off, quit serving images to everyone who comes to the site. Set up a CDN (Content Distribution Network) through a company like SoftLayer or Amazon Web Services. Amazon CloudFront is pretty easy to set up, list your server as the source and their servers do the rest. It’s pretty affordable as well. Drop your website traffic by a third or more so your server can serve out pages and manage accounts.