We should put a hard upper limit on how big the data frames mario is willing to encode to JSON, and issue an error if the data is too big. That's because JSON encoding takes forever with large data frames, and it could also run out of RAM. Doing so will make large dataframes like diamonds fail right away instead of churning for a while on the server (and risking crashing the server altogether), only to timeout and fail after 15-20 seconds, etc.:
We should put a hard upper limit on how big the data frames mario is willing to encode to JSON, and issue an error if the data is too big. That's because JSON encoding takes forever with large data frames, and it could also run out of RAM. Doing so will make large dataframes like
diamonds
fail right away instead of churning for a while on the server (and risking crashing the server altogether), only to timeout and fail after 15-20 seconds, etc.:object_size
might do the trick, but there may be issues with aliasing, etc. still, that could be a good first-pass: http://adv-r.had.co.nz/memory.html#object-sizealso, during the course of doing this, could implement this optimization to save more space too: https://github.com/seankross/mario/issues/28