Varients causing “expotential stress” on Tables

  • mikespo

    (@mikespo)


    4 years ago

    Hello,
    I am building a site that has to do with Cards, mainly trading card games, as you could imagine there are a lot of cards, for example, let’s use Magic The Gathering with roughly 60,000 cards. I used “WP-Import ALL to import all the cards from an Excel File, I now have them all uploaded with pics, I now need to give several variants for “condition” of Card I use the issue that started exponentially creating unnecessary table data BLOATING MY SITE, I believe this has to do with the variations for each card has Ten variations or attributes they are conditions such as – near mint,
    Lightly Played, Moderately played, heavily played, and damaged. Some cards (not all, but this is designated with a taxonomy I used when uploading with WP-import all)also have foils Versions. Duplicating all of those conditions which equate to 10 “options or variants”L I need to showcase in Woocomerce, I will have the price structure based on Percentages less than the “Near Mint Version”

    I was wondering if you guys possibly offer any help or guidance/recommendation that would allow me to accomplish this without Overloading the tables, I did this by creating a variant with WP import (maybe I did it the wrong way) But I created so much Bloat the Website was un-manageable. any help would be appreciated thanks!

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    I’m not a WooCommerce expert, but I’m pretty confident is saying WC does not store product variants in a very efficient manner. For the volume you’re looking at you need a much more efficient scheme. For example, card condition stored in a custom table that’s organized very efficiently. Condition could be stored as a single byte value, allowing for 256 different conditions in one byte of data. Code would need to convert this to and from human readable form like “Lightly Played”, but the storage will be efficient.

    Of course the drawback is you’d need custom code to do this since WC isn’t set up to do things like this. The alternative is to provide much more hardware resource and optimize the tables so the current data schema remains workable.

Viewing 1 replies (of 1 total)
  • The topic ‘Varients causing “expotential stress” on Tables’ is closed to new replies.