nobody, el 24 de mayo a las 20:03 me escribiste: > == Quote from Jason House ([email protected])'s article > > Why not use valgrind? With the GC disabled, it should give accurate results. > > Strange enough, indeed I have tried valgrind with the GC disabled version. It > didn't report anything useful. > > That's why I'm puzzled, does D's GC do something special? > > The GC disabled version run out of 3G memory; but the GC enabled version > stays at > ~800M throughout the run.
I guess that with such amount of memory used, your program can greatly benefit from using NO_SCAN if your 800M of data are plain old data. Did you tried it? And if you never have interior pointers to that data, your program can possibly avoid a lot of false positives due to the conservativism if you use NO_INTERIOR (this is only available if you patch the GC with David Simcha's patch[1]). [1] http://d.puremagic.com/issues/show_bug.cgi?id=2927 -- Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/ ---------------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------------- This is what you get, when you mess with us.
