Wow, that's amazing: what kind of propagators did you use? Normally, domain size is never an issue (Gecode has really the smallest implementation one could think of in terms of memory consumption).
But on the other hand, using sensible domain is an important part of modeling practice: - if domains are too big and domain-consistent propagation is used, then too many holes are created using lots of memory (that must have been your case) - if domains are too big and arithmetic constraints are used, they either have to resort to less efficient numerical types internally or they even might throw an exception due to potential of numerical overflow (Gecode prides itself that it will never silently and incorrectly overflow) So, as always: small is beautiful ;-) All the best Christian -- Christian Schulte, www.ict.kth.se/~cschulte/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Porter Sent: Tuesday, February 26, 2008 4:18 AM To: [EMAIL PROTECTED] Subject: Re: [gecode-users] Heap memory exhaustion It looks like the problem was the domain size. I manually rescaled the domain down by a factor of 100, and it worked (very quickly), even with full recomputation. Thanks for all of your help, -Joe
_______________________________________________ Gecode users mailing list [EMAIL PROTECTED] https://www.gecode.org/mailman/listinfo/gecode-users
