<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Magento sucks!</title>
	<atom:link href="http://future500.nl/magento-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://future500.nl/magento-sucks/</link>
	<description>Advanced Web Solutions</description>
	<lastBuildDate>Tue, 22 Nov 2011 21:40:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Catalin</title>
		<link>http://future500.nl/magento-sucks/comment-page-1/#comment-314</link>
		<dc:creator>Catalin</dc:creator>
		<pubDate>Fri, 23 Jul 2010 11:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://future500.nl/?p=27#comment-314</guid>
		<description>Since Nov 2009 I have been working with magento and now I have a single magento install as a multi-site for almost 40 shops and around 25,000 products. 

Everything is set on a dedicated server (no cpanel, overcomplicated panels - just pure lamp on centos without even email or DNS; we use godaddy and google for those 2 things).

The server is a quad core with 8Gb of RAM and properly tunned for performance with apc-cache and the only thing we are hosting is a magento install for all those 40 domains (shops).

We haven’t added any plugins/features to magento. It’s basically the out of box thing, with a very simple theme added to it.

We have tried all kind of performance tuning and this the best we achieved.

I must admit if people are just browsing the website, it loads very quickly. But the problem is when we update products and orders. It takes about 2 minutes to save a product and it eats 120% of the CPU and 10% from the memory.

Our products are scrapped from other websites, so we need to do regular product updates and let me just tell you that using the dataflow is the fastest way to import products, but even that takes about 1 hour and 10 minutes to process 500 products. So when we have to do batch updates for 11,000 we have to wait endless hours.

If you’re thinking about using magento for your shop, it’s ok, but make sure to have a dedicated server and don’t even try to have more than 10,000 products or a multi-shop. It just doesn’t work.

MAGENTO is simply NOT scalable in performance.</description>
		<content:encoded><![CDATA[<p>Since Nov 2009 I have been working with magento and now I have a single magento install as a multi-site for almost 40 shops and around 25,000 products. </p>
<p>Everything is set on a dedicated server (no cpanel, overcomplicated panels &#8211; just pure lamp on centos without even email or DNS; we use godaddy and google for those 2 things).</p>
<p>The server is a quad core with 8Gb of RAM and properly tunned for performance with apc-cache and the only thing we are hosting is a magento install for all those 40 domains (shops).</p>
<p>We haven’t added any plugins/features to magento. It’s basically the out of box thing, with a very simple theme added to it.</p>
<p>We have tried all kind of performance tuning and this the best we achieved.</p>
<p>I must admit if people are just browsing the website, it loads very quickly. But the problem is when we update products and orders. It takes about 2 minutes to save a product and it eats 120% of the CPU and 10% from the memory.</p>
<p>Our products are scrapped from other websites, so we need to do regular product updates and let me just tell you that using the dataflow is the fastest way to import products, but even that takes about 1 hour and 10 minutes to process 500 products. So when we have to do batch updates for 11,000 we have to wait endless hours.</p>
<p>If you’re thinking about using magento for your shop, it’s ok, but make sure to have a dedicated server and don’t even try to have more than 10,000 products or a multi-shop. It just doesn’t work.</p>
<p>MAGENTO is simply NOT scalable in performance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

