There are good ones on the magento site too (google magento block caching), but its down at the moment. Good starting point is here: - but if you've not used memcached at all before, its worth looking at some general info about it as well. And its dead easy to change it over (relative to doing other magento stuff at least!) I look after a couple of magento installs, and once you get any sort of load on the system, memcached starts to perform much faster. Make sure caching is in memcached, rather than on disk. Solution 2:įurther to Alan Storm's recommendations on caching, there's two things I'd specifically recommend you look into related to caching:
If you're relying on the $7/month plan to see you through, well, good luck with that. The second thing you'll want to do is ensure your host and operations team has experience performance tuning Magento. This will relieve some of the CPU/disk blocking that goes on while Magento is building up its various XML trees. The first thing you can do to ensure better performance is turn caching on (System -> Cache Management). In general, the Magento Engineers were tasked, first and foremost, with building the most flexible, customizable system possible, and worry about performance later. This adds up.īesides the layout system, Magento's template system involves a lot of recursive rendering. This is a powerful feature, but it means anytime a model, helper, or controller is instantiated, extra PHP instructions need to run to determine if an original class file or an override class files is needed. Magento uses its configuration system to allow you to override classes. Also, unless caching is on, these tree are built up from files on disk and on each request. Some of these (especially the layout tree) are huge. This takes both memory (storing the trees) and CPU (parsing the trees). There's a lot of things behind the scenes (application configuration, system config, layout config, etc.) that involve building up giant XML trees in memory and then "querying" those same trees for information. This means querying for a single "thing" often means querying multiple rows Parts of Magento use an EAV database system implemented on top of MySQL.
I've only been tangentially involved in optimizing Magento for performance, but here's a few reasons why the system is so slow
0 kommentar(er)
