Storing data in usermeta and postmeta in the form of JSON whenever possible.
I found that the DB was badly designed (according to me. There might be reasons and I may be wrong.) We have too many rows in usermeta and postmeta just for a single entry. I found that the admin has 16 entries in usermeta itself. When we were supposed to add multivalued data for a single user the table exploded in size. The plugins for a single user the plugins did it all wrong. Unless the multivalued data are supposed to be counted they can be safely stashed in JSON and stored in one entry.
This would greatly enhance the performance.
Can you imagine how dangerous and insane it will be to make those massive DB changes?
Not that this is a bad idea at all, but it's highly difficult to do for sites that are older and large and would suffer greatly if this was done poorly :(
We try to limit the db changes we make for pretty obvious reasons.
We can do it bit by bit. Say for example: nickname, Firstname and Lastname can be put together in a JSON and parsed and shown wherever necessary. Plugin makers of magic field and all can be directed to make necessary changes to group and put everything in json format.
If none of this is possible we can design and implement a real good database in WordPress V (version 5.0). I believe that those older sites can gradually make changes and get along but it would be an injustice for newer sites if we continue like this. IMO we should never put aside good ideas.
We're not going to ever do a total rewrite, and FWIW the number of the release is not as ... major as people seem to think it might be. We just go 1.0 to 1.1 and up by points all the way, semantic :)
Would this real save a lot of size except in number of tables?
RSS feed for this topic
You must log in to post.