我们在生产机器(VCenter虚拟机,4核,8 GB内存)的ubuntu 12上使用nginx和php5-fpm.我们的magento安装主题和扩展.前几天我只是为了踢一下而已,将所有内容从头安装在VMWare盒中,并默认安装了Magento 1.12 EE(我需要在bug上大喊大叫).我只是这么说,所以您知道我们已经在生产环境中使用了nginx和php5-fpm.
…However, the problem is indeed Magento, rather than the configuration
of the server. Magento is just too large and too heavy to any
environment. Magento hosting is really tedious and unpleasant task.
Magento makes heavy use of the disk subsystem for many of its
operations. Disk I/O is the biggest bottleneck, next to CPU’s
(cores), to optimal Magento performance.
This is why Magento performs so poorly in cloud environments where the
storage is on a SAN shared with countless other users and under stress
at random times causing inconsistent performance.
SSD’s (Solid State Drives) configured in a RAID1+0 disk array locally
outperforms 15.5K SAS drives in the same RAID configuration.
A local Database is also the key to peak performance with Magento
A remote database introduces latency due system calls and network
saturation. If you must use a remote database you should make sure
you are on a private VLAN and not sharing an over saturated network
connection, which is common for even the largest hosting providers.
In the best of network environments, remote database will NOT be as
fast as local database for a variety of reasons.
CPU speed and the number of CPU’s is also incredibly important to
optimal Magento performance. You can get an idea of the power of the
high end CPU that you are using at the following URL – if the CPU is
not listed here it is not considered ‘high end‘ by the benchmark
Performance based web servers, such as LiteSpeed, make use of multiple
CPU’s (cores) as does the MySQL server, with a proper configuration.
Using a performance based web server can significantly improve your
applications performance against the Apache web server software.
Trying to rewrite or convert/compile Magento is not a solution – it’s
a bandaid at best. You will be locked out of any future upgrades
(without a significant amount of development time to rewrite and test
your changes) and with each upgrade we continue to see speed
improvements. Core changes to Magento should NEVER be performed, core
changes to Magento should NEVER be performed – this defeats the OOP
model that Magento employs.
In the end, as we have said before, Magento can not achieve optimal
performance without a significant investment in the infrastructure on
which the application runs. If you are considering running Magento
and are wanting to do so on a budget hosting provider understand that
you simply can not and will not achieve peak performance with this
Magento requires resources due to it’s complex nature – you can not
provide the necessary resources on a budget hosting provider as the
costs for this type of hardware system is not inexpensive.