email@example.com (Andreas Bernauer) writes:
> If I leave a newly started scsh alone, its memory usage increases to
> 14M in about 2 hours.
Thanks, it's nice to know this happens on Linux, too. I see the same
behavior running ,collect that you do.
firstname.lastname@example.org (Eric Knauel) writes:
> I think that's an OS issue. scsh allocates memory for the heap, but
> the OS does not assign this memory chunk immediately.
> When fired up scsh tries to allocate 10 MB, but gets less. This is
> related to the memory allocation strategy of the OS. Bit by bit the OS
> will assign the rest of the 10 MB in 4 k chunks to scsh (4 k is the
> page size). So it should stop growing when the OS has assigned the
> whole memory which scsh requested. And it does. ;-) We have a scsh
> based web server (scsh.net) up and running for two months now and it
> uses the same amount of memory as on the first day. ;-)
And thanks for the reassurance + explanation. I left the REPL up all
day and it hasn't grown beyond 19852K. A couple of hours ago I fired
up a process that does something (generates a new picture for the root
window) every 5 seconds and it quickly grew to 19852K, but it hasn't
grown past that. I'll let it run all night. (Probably what I should
have done in the first place, but I learned good stuff by asking.)
And just finished reading a post from Mike Sperber on comp.lang.scheme
about a (not too soon) native code compiler for Scheme 48. Scsh is
great fun now and later it'll be faster. (It's fast enough now for
most of what I've been doing with it.) I'm ending the evening on a
I have made this letter longer than usual because I lack the time to
make it shorter.
-- Blaise Pascal