[m-dev.] benchmarks for fixed size trail versus trail segments
Julien Fischer
juliensf at csse.unimelb.edu.au
Thu Sep 4 09:02:01 AEST 2008
Hi,
Here are some timings for the trail segment change.
Julien.
----------------
hlc.gc.tr vs. hlc.gc.trseg for the G12 FD benchmarks.
The fixed size trail is 65,536 kilowords -- it needs to that
big in order to avoid trail exhaustion ;-)
The segment size is 32 kilowords.
Test Fixed size Segments
---- ---------- ----------
alpha 710 ms 500 ms
bridge 500 ms 370 ms
cars 560 ms 350 ms
contig_bench 1210 ms 1070 ms
test_element 1000 ms 900 ms
test_element 570 ms 400 ms
eq10 670 ms 470 ms
eq20 670 ms 470 ms
queens 780 ms 620 ms
queens_ff 250 720 ms 790 ms
sendmoney 260 ms 50 ms
sudoku 480 ms 450 ms
steiner 2,3,7 270 ms 50 ms
steiner 2,3,15 580 ms 400 ms
steiner 2,3,31 7450 ms 7820 ms
steiner 2,4,13 7670 ms 7750 ms
steiner 2,5,21 520 ms 310 ms
steiner 3,4,8 6930 ms 7930 ms
steiner 3,4,16 7220 ms 7630 ms
steiner 3,6,22 4190 ms 4450 ms
queens_ff 500 2270 ms 3000 ms
steiner 2,3,9 79590 ms 81350 ms
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions: mercury-developers-request at csse.unimelb.edu.au
--------------------------------------------------------------------------
More information about the developers
mailing list