I seem to remember that Catalog was always advertised as being capable of managing "10,000 products". I'm currently developing a store which has a little over 3000 products, *but*, they each have a rather complicated component pricing model attached and I'm becoming concerned that Catalog might choke on it.
Every product uses the same component for pricing purposes, consisting of three attributes. The attribute choices, combined, amount to 770 possible permutations per product, although only 124 of these permutations are valid (and I've removed all invalid permutations from the list). That's 2,410,870 permutations - but only 388,244 are valid permutations - per product on 3131 products.
So... Should Catalog be able to run with this sort of a load on a "typical" desktop PC? So far I've imported all the products, added the component model to 60 products for development purposes and Catalog now seems to take an awfully long time to start up on my Athlon XP2600+ box, although XP is only reporting it as using 19Mb. Also, the process of pasting the component model into new products seemed to be slowing down to around a couple of seconds by the time I'd done fifty or so of them.
If this is a definite no-no, is there any way to "reference" a component pricing model from one product into all the others, rather than duplicating it?
Every product uses the same component for pricing purposes, consisting of three attributes. The attribute choices, combined, amount to 770 possible permutations per product, although only 124 of these permutations are valid (and I've removed all invalid permutations from the list). That's 2,410,870 permutations - but only 388,244 are valid permutations - per product on 3131 products.
So... Should Catalog be able to run with this sort of a load on a "typical" desktop PC? So far I've imported all the products, added the component model to 60 products for development purposes and Catalog now seems to take an awfully long time to start up on my Athlon XP2600+ box, although XP is only reporting it as using 19Mb. Also, the process of pasting the component model into new products seemed to be slowing down to around a couple of seconds by the time I'd done fifty or so of them.
If this is a definite no-no, is there any way to "reference" a component pricing model from one product into all the others, rather than duplicating it?
Comment