Note that there are some explanatory texts on larger screens.

plurals
  1. POMagento increase bad performance for applying catalog rules
    primarykey
    data
    text
    <p>I am experiencing problems with my magento store.</p> <p>We currently have +- 700 catalog rules setup for all our customers. On a catalog with 2800 products (configurable and simple) and 80 attributes. </p> <p>Magento version: 1.7.0.2 Compilation: off Category/product: flattened Cache: all enabled Indexes: all enabled</p> <p>Applying the 700 discount rules via the magento GUI takes forever (>30 min), without getting any feedback. Afterwards no rule gets applied. I have tried a shell script found here: <a href="http://browse.feedreader.com/c/Drew_Gillson/232210211" rel="nofollow">http://browse.feedreader.com/c/Drew_Gillson/232210211</a>. This way I get a lot of feedback when the rules get applied, and about the time it takes to apply rules to a product. What I see is that it takes approximately 2 seconds per product to apply all the rules. This means that applying all the rules will take 2s * 2800 = 4200s / 60 / 60 = 1:10 hours This is of course an unacceptable performance issue. As the CPU and RAM usage goes to the roof. Server which this is hosted on is a VPS with 4GB of RAM (3.5GB free) and 4 dedicated CPU cores. (xeon 2.4GHZ)</p> <p>When I decrease the number of catalog rules to +- 25, the performance is acceptable (couple of minutes). But for our case we would like to make use of a lot of catalog rules, due to different pricing agreements for different customers. </p> <p>Is this possible with Magento Catalog Rules? Or is there another way to efficiently generate 'catalogrule_product_price' rows in the database, based on the catalog rules.</p> <p>Thanks,</p> <p>Wouter</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload