Hi! I have been looking more specifically at what the (UCI) engine does to memory consumption.
I start Scid. It does some preloading of stuff, I hit OK at the startup window and let the clipbase and new empty game come up. At the end of the scid_InitTclTk() in tkscid.ccp, Scid has eaten 23706940 bytes from the heap. Now I start the engine, let it spend its efforts on the start position in the game, in single variation mode. Each time the engine presents a new line, Game::Decode() is called several times allocating some more memory, and giving me the opportunity to drop some heap statistics in the console. By the time Game::Decode is called for the first time, Scid eats 26077955 bytes. So after the init function some extra 3 MB has been consumed. Never mind, the very end of initialization must be somewhere else. Impossible for me to understand is that Scid eats more and more memory with each line (I think even with each move in each line) the engine presents: By the time the engine suggests 1.e4 c5 at depth 15 (after some 5.4 seconds), memory consumption has gone up to 28807555 (!). What useful things could Scid possibly do with those costly 2MB? Cheers, Joost. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
