I have a web application with medium-high traffic where users can save designs made by fabricjs, so each saved design is a json with many parameters.
So basically two days after launch users have stored almost 300 rows of designs, PhpMyAdmin says a total of 31 MB of size.
Each json is stored as a longtext data type so I'm concerned about the increase size of the database with time.
I've checked the COMPRESS MySQL function and made some tests about it and the conclusion is that the compression ratio is about 30 - 40%, so it may be a bit low for what I want to achieve.
Another thing to know is that the saving process is automatically made by the application (this is a must by requirement), so when user downloads the design as a PNG file, its json automatically saved. All the saved designs can be continued on any other moment by user.
My goal is try to minimize space consuming in my server, is saving as files filesystem a valid alternative to minimize MySQL size (so don't penalize queries performance) or it would penalize server's CPU load times with read & write disk operations?