Dear Filip,
in my experience, a good start point for memory problems with Oz is to start
with a little problem with the same distribution and search strategy in the
Explorer.
Many problems I found derived from my bad distribution (and propagation) strategy
causing the explosion in the search tree and because of that a huge memory and time
comsumption.
Cheers,
Adriano
Hi,
this is definitely not the problem. I use a new search script inside
each loop, and in fact there are 2 levels of search (the subproblems are
solved using IOzSeF via a port), so the Explorer is out of question
anyway :-) But the size of the search tree is ok, no problem. Each
iteration takes about 2-15s (hard problems up to 40s) to solve, and
sometimes it takes about 600MB to solve, but after the solution is
found, I think that not all of that memory is released, which in time
leads to swapping (which totally kills performance).
Thank you for your comments, though!
Cheers,
Filip
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
