Hello Esa, Sunday, August 20, 2006, 7:35:16 PM, you wrote:
> Bulat, my apologies if you're not interested in details, but I recall > you took part in the earlier discussion about this issue. Would you > be interested at testing this or final patch? I read the patch and it seems that your in general properly implements Simon's idea of creating linked list of memory blocks allocated. i'm don't want to build ghc myself, and rather limited in downloading large files so i'm sorry that i can't test your patch on real programs > * Memory is only committed when actually given to the rts/gc, so > reserving big chunks is still a valid tactic - reserving memory only > takes address space, it doesn't show in memory use or take space in > pagefile. first, this still shows up in more detailed process exploring utilities. it's not a real problem, but still some inconvenience what's more important - address space may be valuable resource in some cases. my own program uses C libraries in order to compress data. these libraries allocates large memory blocks by itself, so reserving 256 mb of memory space means that compression routines may use for compression no more that 1.75 gb of memory instead of 2gb. It's not a principal problem again, but think about program run, say, with -M1g switch. is this program will reserve 1gb of address space just for case? if it is possible, it will be best to reserve memory in small chunks -- Best regards, Bulat mailto:[EMAIL PROTECTED] _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
