Handling large N data in WordPress

  1. Custom table(s). WordPress posts are not structurally a fit for what you are doing. Trying to use them for this will result in a lot of unnecessary data processing and storage. But you need to think through your own database design and you need to be good with SQL or you will end up inefficient anyway.

  2. I am not convinced transients will help you here. It sounds like you are going to altering data a lot. That may negate the benefits.

  3. Serialize if you must store an array. JSON might be smaller but serialize has more data– a kind of simple checksum value for one. Size shouldn’t matter. The option_value column of wp_options is longtext. That is about 4GB. The limiting factor is going to be system memory, not the column.

  4. Client side processing (Javascript) is many, many times slower than server side (PHP) not to mention the data transfer time. If you have prepared data in a transient that might help, but as before it sounds like you are going to be altering data a lot.

  5. No idea what this means.