Super fast..... I am very excited to see this new speed..... I have attached the new proxy.php file that was taking up a lot of the speed. Replace this one with your old on and see what speed is all about
Thank you Yoav and Magento for this new file and all that you have done for putting the power back in to the hand of the owner..
There is a definite improvement there, but I am receiving an error when viewing one of your pages. The error is:
Fatal error: Class 'Mage_Catalog_Block_Product_Featured' not found in /home/hbaetcco/domains/hbaetc.com/public_html/magento/app/code/core/Mage/Core/Model/Layout.php on line 442
No not yet. for the past 2- 3 weeks i have been playing with Magento more then i have been doing my job, so i have to do some work today, i juss i will play Magento when i get home
I updated my proxy.php file, i’ve tried cache on, cache off, and regardless, it’s still so slow, it’s unusable. I’m sure there are many others having this problem - is the problem being analyzed more closely by anyone on the team? I’m under the gun to finalize a commerce solution, and really really wanted to use magento, but with this issue, it’s looking like I won’t be able to.
There is something wrong with how Magento is built, wether it’s the SQL Queries or the PHP I have never had any other issues with performance and speed like I go with this…
I’m not so surprised as this is open source! Still though, I too am under pressure for an ecommerce platform and need one ASAP. Was really excited about Magento until I opened the homepage. Spent most of today reading a multitude of forums and blogs about the slow performance, but still no joy. This really only looks like a package for big companies with their own dedicated hosting unfortunatly.
I have a performance enhancement that may reduce strongly the mysql query time to build the category tree : the nested set model. This would dramatically reduce the page load time for the first time user with lots of categories and products (problems described before in this post), when the cache does not contain the page yet.
The counterpart is that it would require to rethink the table structures, but from my experience it’s worth doing it. It requires also more queries to insert data but this is not very problematic here.
@PitchOu - Thank you for your proposal. We have already played around with the “Nested Set Model” but found that the “Materialized Path” was a better fit for us.
I am still interested if you have any numbers to compare the two approaches.
Even with version 1.0, I still see 20s plus page-load times with large catalogs (2000+ categories, 40000+ products) for the catalog/category pages. Will we see improvement in this area soon or do the people with large catalogs just have to deal with the long page loads?
@webfxmasta - By catalog/category pages, are you referring to the search results?? In case you are, search in Magento is a “LIKE based” search and is bound to be slow for huge catalogs. You need to customize to store your search relevant field values separately and index them to get better search time ....
But I see a poor performance on the home page itself and wish it is improved ...
No not the search results...just the basic Catalog/Category navigation pages. (Ex. http://www.my-magento-store.com/catalog/category/view/id/3/) I’m not worried about the search speed just yet. I want to try to get the basic Catalog browsing as fast as possible first.
