Community vs Enterprise Edition – speed test

Community vs Enterprise Edition – speed test

Recently I made a speed test between Magento Community Edition (ver. and Magento Enterprise Edition (ver. Here, I will show you the results of that test with short explanation of the testing procedure. For the purpose of testing, I made a little modification in index.php file from both of magento instances.
I put

$start_time = microtime(true);

at the beginning, and

echo microtime(true) - $start_time;

at the end of the index.php file.
That allowed me to measure and print the execution time for each request (time is displayed as a floating point number in seconds).
The test was separated in three parts. First part was to measure response time for CMS page (cms/index/index in my case), second part was category page (catalog/category/view/id/5) and the third part was product page (catalog/product/view/id/19).
Magento Community Edition was tested both with and without cache enabled.
Enterprise Edition was tested in three variantes: first was with all cache disabled, second was with all cache enabled except full page cache (like the cache from Community Edition), and the third was with all cache enabled.

Community Edition

CMS page

Category page

Product page

Enterprise Edition

CMS page

Category page

Product page

Final comparison

CMS page

Category page

Product page

Final comparison is derived from previous tests for cases when all cache available is enabled, both for Enterprise and Community edition.
Whole test is created at the same machine with default Magento installations with sample data. There has been 20 requests per each test case. Tests are automated using Selenium testing system.

You made it all the way down here so you must have enjoyed this post! You may also like:

Calling out all Magento developers who want to improve their testing skills – visit MageTestFest! Maja Kardum
Maja Kardum, | 0

Calling out all Magento developers who want to improve their testing skills – visit MageTestFest!

Review: MageTestFest – testing all the way! Stjepan Udovicic
, | 0

Review: MageTestFest – testing all the way!

Why you should go to MageTestFest if you are a Magento developer Maja Kardum
Maja Kardum, | 0

Why you should go to MageTestFest if you are a Magento developer


  1. Thanks for the interesting test like this. To be honest, I have never used magento enterprise because no client want to pay for it. It’s too expensive for some additional features. In my opinion, Magento runs fast if you optimize its speed. I often use Google Page Insight to know what to fix. If it still runs slowly, i use extension. My favourite one is Full Page Cache at . It works well with Magento 🙂

  2. magento enterprise is too expensive. and I didn’t use any Full Page Cache in Community Edition too.But I think my magento is fast enough.

  3. Well, I used magento for a long time but still have no any customer willing try Enterprise version. Maybe this is one of very good article to get them try with better version. Thanks

  4. What magento theme was used for EE and CE for testing?
    Maybe EE Theme has less blocks on pages then CE?

    How you may explain difference in results without cache?

    Looks like if CE develop in proper way it’s no need any FPC service, because generation with cache show results near 1 seconds.

  5. Well, good to know.
    I have never used magento enterprise because no client want to pay for it. Too expensive for some additional features.

  6. In my personal experience there is no point to compare those two in any other way than purely philosophical. At the end of the day, server infrastructure is what counts. I saw EE so slow that I could cry and community so fast that you you can’t believe it is Magento 🙂
    It is not the speed that you buy with EE, it is mostly features. If you don’t need those, you should go community, however if you plan to utilize any of EE features then go EE. Idea of having EE features on top of CE by using extensions is quite naive unless you plan to code those extension by your team (which btw needs to be very good) which would raise the cost of CE additional development much more than purchasing EE. At least that’s what counts if you are going for some serious business.
    Not to go into the details, but having FPC (using EE fpc or Varnish) is definitely just not the main thing you should rely upon when you want fast site. It helps, but it is nothing THAT special. You can make whatever kind of FPC, but if your site sucks, if will suck with or without. 😉

  7. Community with full page caching would get the same results as Enterprise with full page caching. Comparing community without FPC with enterprise with FPC is not a good way to approach it, using your community + cache – FPC vs enterprise + cache – FPC is more far comparison. We run lightspeed extension and it gives same results as enterprise FPC. -> one off $500 extension cheaper than $14,420 annually. though of course magento enterprise has more stuff, but for $14,420 annually, i’d rather get community and hire a company like to deck it out and i reckon you would get better support from development company. Magento ‘enterprise’ support is code word for $500 per hour ‘support’ from a $10 per hour outsourced programmer you don’t work with face to face.

  8. Very interesting. The results are not spectacular, though. Full page cache is great if you use a default magento installation, but when the client requirements start to grow, cache needs to be re-thought and Varnish works much better for this purpose. Installing varnish and ajaxifying the blocks that don’t have to be cached… that’s the way to success!

  9. According to the implementations I was involved in (5 EE this year, 20+ CE), EE is slower than CE (if FPC is not used) because of the overhead from other stuff (like events and additional observers/events and so on)…
    Using a FPC module on CE gets you same/better performance.

  10. @MilenPetrov It’s very likely that this option has no effekt in your store because your server doesn’t support it. Do you use a Zend server?

  11. Would be interesting to compare the results with and without it. Probably the results will significantly change

  12. Zvonimir, I am curious whether when you did your tests did you enable full page cahces on CE 1.6.1 from System->Configuration->Advanced->System->External Full Page Cache Settings, and how ebnabling/disabling this option affects the results.

  13. Please put a product in your cart, login or change sort order of category page in order to drop out of full page caching. Your test result will differ.
    I’m happy with ce and extensions like zoom cache and varnish.

  14. I notice you did a review on the tinybrick lightspeed extension. Can you do a post which compares the Enterprise Edition Full Page Cache vs the LightSpeed Full Page Cache? Lightspeed features holepunching, but how does EE FPC tackle the issue?
    Also in CE under Advanced > System, there is an option for External Full Page Cache Settings but apparently this only works with Zend Server? As that features Zend Page Cache, which is the controller to have this feature in CE.
    Could you explain more about this too please?

  15. Great post, however the graphs are not made for easy comparison, some range 0-6 seconds, others only 2-4seconds. So it doesnt fairly show the speed difference, if you look at the CE Category page graph, and compare it to the EE Category page graph.
    EE is actually slower than CE, but your graphs are done wrong to not show this.
    Please make all the graphs range 0-MAX, so if you have one graph 0-6 seconds, make them all like this so you can clearly visually compare, otherwise, don’t do graphs, and post a text table instead.

  16. This best thing for community is to spend a little bit of money and get FPC system for community. This will save you a lot of money since it’s around $350-500 for a good one with support vs $12k a year for EE. EE is not worth it if it is just for the speed. It’s the things like flash sale abilities that make it $12K but even that is hard to justify.

  17. Is there a way to create this full cache on CE with a extension? How does this full cache meganism work?

  18. Tests are created on my local machine which is pretty slow (not on a real server).
    There are also many other ways to speed up your website besides default Magento cache (eg. APC).
    So, if you configure your server on a right way, Magento Community Edition should work great!

  19. EE is basically CE with some additional modules, right? Obviously the FPC is going to be far faster than CE without it, but fortunately there are some decent FPC modules for CE out there. CE is considerably faster with no caching vs EE with no caching which shows that EE is basically the same, just heavier (larger config and layouts, more event observers, etc).

  20. Even worse, huh? I realize Community edition is a free product but IMHO Magento ought to fix this discrepancy. After all, it only reflects poorly on them if one of their products is sub-standard.

  21. Hello Michael,
    numbers are given in seconds.
    Here is the average calculation for final comparison:

    CMS page
    Community Edition: 0.657307744026185 s
    Enterprise Edition: 0.178545629978181 s
    — Community edition is 7.86814269612009 times slower (1.90812920331953 s).

    Category page
    Community Edition: 2.18595237731932 s
    Enterprise Edition: 0.277823173999786 s
    — Community edition is 4.28337550284117 times slower (1.00306845903396 s).

    Product page
    Community Edition: 1.30856761932373 s
    Enterprise Edition: 0.305499160289766 s
    — Community edition is 3.68145523419705 times slower (0.478762114048003 s).

  22. So $12k/year gets you ~1–2ms? 😉

    Can’t say I’m surprised but its a little disappointing to see. Sure the paid edition should have more features etc. but the community edition is dreadfully slow and apparently Magento aren’t too concerned about fixing that? Lame.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <blockquote cite=""> <code> <del datetime=""> <em> <s> <strike> <strong>. You may use following syntax for source code: <pre><code>$current = "Inchoo";</code></pre>.

Tell us about your project

Drop us a line. We'd love to know more about your project.