Good morning, Thank you both for your replies. > Another hint: if your model uses the standard Gecode search engines, you can > inquire how much memory is occupied by the nodes of the search tree. If > there is a huge difference between what is reported by the search engine and > what is reported by your operating system, you program just has a memory > leak. > I indeed use a standard Gecode search engine (Branch-and-Bound). I followed you advice and performed the test: both values are coherent. > Then, how deep is the search tree? How many variables and propagators does > your problem have? > Here are the figures: - Variables: 622 - Propagators: 25654 - Deep: 49
> In the end: we could say much more if you provided a little bit more detail > about what you observe. The information that your program uses a lot of > memory is not that helpful in itself. > Mea culpa: the memory consumption reaches 862MB. My message was inaccurate yesterday evening: the memory peak occurs when the engine constructor is called. It's maybe consistent with the figures provided above ? BenoƮt _______________________________________________ Gecode users mailing list us...@gecode.org https://www.gecode.org/mailman/listinfo/gecode-users