I'm also guessing the jump from 600MB to 3GB is related to encodings. The
file is probably UTF8/ASCII, and racket strings are a different encoding. I
think they're one of the 32-bit encodings? So for ASCII text that alone
would be a factor of four increase in memory usage.
port->lines produces a list with all the lines in it. That list is what
uses all the memory. Using in-lines avoids producing the whole list at
On Thu, Sep 24, 2020, 8:53 AM Hong Yang wrote:
> Thanks Laurent, I tried (in-lines...), and yes, it's memory-efficient, but
> I still curious
Thanks Laurent, I tried (in-lines...), and yes, it's memory-efficient, but
I still curious and concern why (port->lines ...) takes so many memory.
On Thursday, September 24, 2020 at 6:55:10 PM UTC+8 laurent...@gmail.com
> Quick comment: of you don't need to load the
Quick comment: of you don't need to load the whole file but want to parse
it line by line, use `in-lines` which is memory-efficient.
On Thu, Sep 24, 2020, 11:46 Hong Yang wrote:
> Update with memory dump log attached.
> 1. With out (set! input empty), call (collect-garbage) doesn't help
Update with memory dump log attached.
1. With out (set! input empty), call (collect-garbage) doesn't help
2. Call (set! input empty) and (collect-garbage), memory reduce dramaticly.
; 214M(VIRT)/101M(RSS) without open any file
(sleep 5) ; Waiting here so that I can check
Mail list logo