3 ms·
imo, json dt should be an intermidiary step in db struc in rdb, never the final. Once you know & have stable columes, unravel the json into proper cols with ind
by taesu 5y ago
imo, json dt should be an intermidiary step in db struc in rdb, never the final. Once you know & have stable columes, unravel the json into proper cols with indexing, it should improve the situation
if youre having issues with 5gb, you will face exponential problems when it grows due to lack of indexing
- k1rcher 5y agoCheers for the response (and affirmation). After some latency profiling I am convinced proper cols with indexing will vastly improve our situation since the queries themselves are very simple.
- taesu 5y agoYou can take incremental approach and p.o.c with the data that you have so you can justify your move too!
- esemathew 5y agoDepending on how much of the data in your json payload is required, extract data into their own table/cols. And store the full payload in a file system/cloud storage.
- machiaweliczny 5y agoAlso there's a way to profile which queries take longest via DB itself and then just run EXPLAIN ANALYZE to figure what's wrong