Database queries - too many?

[Anna718]

I am currently in the process of setting up my site, but one thing I have notice is that the number of database queries on a product page are through the roof.

I only have two products listed right now, though more will follow and on the product pages I am seeing 570 and 672 database queries, depending on which product I go to.

I also run an Invision forum, and the worst page on that site, with a lot of extras, only results in about 60 queries per pageload.

Why are there so many queries on a product page load for zen cart? 672 queries is a little over the top.

I run image handler 2, have downloads turned off, and also have category counts turned off. I really want to reduce this before I go live.

You can check out my site at RT Gallery username "Tester" password "user" (without quotes) both are case sensitive

Any suggestions would be appreciated. Thanks

[yellow1912]

I am currently in the process of setting up my site, but one thing I have notice is that the number of database queries on a product page are through the roof.

I only have two products listed right now, though more will follow and on the product pages I am seeing 570 and 672 database queries, depending on which product I go to.

I also run an Invision forum, and the worst page on that site, with a lot of extras, only results in about 60 queries per pageload.

Why are there so many queries on a product page load for zen cart? 672 queries is a little over the top.

I run image handler 2, have downloads turned off, and also have category counts turned off. I really want to reduce this before I go live.

You can check out my site at RT Gallery username "Tester" password "user" (without quotes) both are case sensitive

Any suggestions would be appreciated. Thanks

This will be addressed in v1.4.0 releasing this month (or so I heard)

[gjh42]

Version 1.4 (theoretically due out this year - we'll see) addresses this in a big way.
See the roadmap in the Zen Cart Release Announcements forum.

[Anna718]

Thanks yellow1912.

I certainly hope it is, as this is over the top.

[DrByte]

LOL ... keep in mind ... unlike a forum, with an ecommerce site you're dealing with display and calculation of sales, specials, taxes, extra sideboxes for displaying different pieces of information in different ways, product listings, categories, images, etc.

That said, it's a well-known fact that v1.3 and earlier inherited some bad query structures from the initial code base. A huge amount of that has been rewritten for 1.4, as explained above, and detailed in the roadmap.

[Anna718]

Understandable Sensei, but on my forum, which is very heavily modified, there are probably more individual pieces of data being displayed that I see on my product pages. As for images, they do not cause database queries, or at least they should not, and my forum has heavy graphics, with images up to 10Mb each in place sometimes 30 to a page.

I have zero tax rates, no specials, zero reviews, and only two products in one category right now. I shudder to think what will happen once the store is fully populated.

IT worries me as my hosts have a limit on 20,000 database queries per hour, and with 670+ queries on a single page load, that limit can be reached far too quickly. No page requires 670 database queries, especially when 99.9999999% of the information is static, the only thing that might change is the stock level.

[yellow1912]

The category tree is the main cause for the current number of queries. Especially if you have too many categories.

You may consider caching it and other blocks that may use too many queries
http://www.zen-cart.com/forum/showth...ighlight=cache

Or use an alternative category tree that uses less query.
This one for example, using a single query along with caching as well:
http://www.zen-cart.com/forum/showth...+category+tree

Or you can wait till 1.4 coming out, please make it an XMAS gift for us, DrByte

[Anna718]

Thanks yellow1912, but I would prefer to avoid caching the product pages as stock levels will be strictly limited, and although I could manage that with cron, I just prefer not to.

One thing that I do not understand is that if you look at the two product pages I currently have in place, the first has 8 options for attributes and the second has 6 options. Why would there be around 100 extra database queries for the first than the second, when all other page details are identical? Two more options creates 100 database queries does not make programming logic sense????

Please bring on 1.4

[DrByte]

Again, you can thank the folks over at the other shopping cart that wrote the original attributes code with a weak database structure and bloated inefficient coding.
The 1.4 version will make a huge difference in performance in these areas.

[stonecoldinc]

Cool Website, What tool did you use to handle your Pics?