[Haskell-cafe] Aeson memory use
saurabhnanda at gmail.com
Thu Aug 9 18:38:00 UTC 2018
This is interesting. Why would something like a Data.Map have a bad memory
footprint? In your Aeson benchmark, what happens to memory usage if you
manually trigger a GC cycle? Is hundreds of megs of memory actively being
used? Or is most of it garbage waiting to be collected?
On Thu 9 Aug, 2018, 9:38 PM Lana Black, <lanablack at amok.cc> wrote:
> On 08/09/2018 02:38 PM, Vanessa McHale wrote:
> > Well, the problem with that is that in a lazy language, the "parsing
> > stage" may not be as clearly distinguished as you suggest. Simply
> > forcing the evaluation of all THUNKs is not what happens in the actual
> > program.
> True. Unfortunately, that doesn't mean the memory issue doesn't exist.
> Data.Map already has quite significant memory footprint, but aeson makes
> it even worse.
> Haskell-Cafe mailing list
> To (un)subscribe, modify options or view archives go to:
> Only members subscribed via the mailman list are allowed to post.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe