Niels, It's hard to me to create a demo script, but at leats I'd want to know if it's a known "issue" (maybe it's not an issue, just as Monet works internally)
I can tell you that a table with 100 columns (ints, varchars, dates, etc) with 30 million records, may occupy 30 Gb of disk. When I merge some of these columns into one new json column -(i.e. 5 single columns into one object like {col1:value, col2:value...}- and dropped the 5 old columns (already merged in json), the table now grows upto 100 Gb of disk.
Thanks
El jue, 22 sept 2022 a la(s) 10:35, Niels Nes (niels.nes@monetdbsolutions.com) escribió:
Alberto
Do you have some script which replicates this issue? And could you post the issue on the github issues?
Niels
On Thu, Sep 22, 2022 at 07:57:07AM -0300, Alberto Ferrari wrote:
Hi all:
Monet version 11.35.19 (Nov2019-SP3)
We realized that json columns in any table produces bigger stored disk, no matter how many rows has big data. It seems like depends on rows with different values in same json column: if many rows has different values, then the space on disk increases exponentially. So we can't use jaon columns in big tables, since we run out of space disk in short time. (also tested with 11.43.5 -Jan2022, same issue)
Is there any solution to this problem? Tanks! Alberto _______________________________________________ users-list mailing list -- users-list@monetdb.org To unsubscribe send an email to users-list-leave@monetdb.org
users-list mailing list -- users-list@monetdb.org To unsubscribe send an email to users-list-leave@monetdb.org