Trace number 233618

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
Tramontane 2006-12-04SAT 0.396939 0.398932

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-100-1.xml
MD5SUMd022748892add36e7fd0a0a2d512e1b7
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.396939
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size957
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3150
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.02	c 	variables.............    0
0.02	c 	predicates............    0
0.02	c 	constraints........... 0.21
0.22	c Allocating memory
0.22	c 
0.22	c time limit = -1
0.22	c heuristic = dom/wdeg
0.22	c restart policy = Geometric increment
0.22	c restart base = 149
0.22	c restart factor = 1.33
0.22	c 
0.22	c Solving
0.22	c
0.38	s SATISFIABLE
0.38	v 0 784 402 897 472 830 306 94 244 631 53 712 539 177 872 768 76 642 164 854 253 0 482 388 603 560 710 317 117 687 50 170 388 525 101 611 660 117 461 317 254 481 0 695 247 631 260 422 823 725 566 25 453 774 329 880 499 611 134 42 344 197 527 244 371 49 436 248 872 619 784 0 164 583 105 0 920 497 592 274 405 720 94 635 886 387 173 835 101 371 104 705 666 400 851 342 762 483 581 134 931 171 280 593 0 188 0 890 486 99 542 292 660 665 623 832 387 854 814 741 171 0 486 76 879 297 395 682 540 762 566 623 854 632 200 880 199 559 105 768 686 429 631 278 482 335 0 15 833 344 444 542 724 99 171 483 402 0 904 666 253 15 335 802 634 342 400 187 254 741 642 278 156 566 0 76 525 429 581 831 370 686 99 765 53 177 557 812 306 459 254 619 0 170 854 313 725 76 226 117 528 289 0 395 812 444 200 631 342 854 583 243 497 342 370 60 197 146 712 292 188 0 453 660 814
0.38	d          SAT       790 BTS      0.13 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node40/watcher-233618-1168327114 -o ROOT/results/node40/solver-233618-1168327114 -C 1800 -M 900 /tmp/evaluation/233618-1168327114/tramontane/bin/solver /tmp/evaluation/233618-1168327114/unknown.xml -res geom -f 3 -v 1 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 2.13 2.18 2.01 3/84 21708
/proc/meminfo: memFree=737992/2055920 swapFree=4192812/4192956
[pid=21707] ppid=21705 vsize=6792 CPUtime=0
/proc/21707/stat : 21707 (solver) R 21705 21707 19940 0 -1 4194304 433 0 0 0 0 0 0 0 18 0 1 0 181110827 6955008 412 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 6880120 0 0 4096 0 0 0 0 17 0 0 0
/proc/21707/statm: 1698 413 374 92 0 30 0

[startup+0.109058 s]
/proc/loadavg: 2.13 2.18 2.01 3/84 21708
/proc/meminfo: memFree=737992/2055920 swapFree=4192812/4192956
[pid=21707] ppid=21705 vsize=8368 CPUtime=0.09
/proc/21707/stat : 21707 (solver) R 21705 21707 19940 0 -1 4194304 1171 0 0 0 9 0 0 0 18 0 1 0 181110827 8568832 1139 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4158501395 0 0 4096 0 0 0 0 17 0 0 0
/proc/21707/statm: 2092 1139 705 92 0 436 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8368

Child status: 0
Real time (s): 0.398932
CPU time (s): 0.396939
CPU user time (s): 0.374943
CPU system time (s): 0.021996
CPU usage (%): 99.5004
Max. virtual memory (cumulated for all children) (KiB): 15380

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.374943
system time used= 0.021996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2949
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 13
involuntary context switches= 62

runsolver used 0.003999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node40 on Tue Jan  9 07:18:35 UTC 2007


IDJOB= 233618
IDBENCH= 6620
FILE ID= node40/233618-1168327114

PBS_JOBID= 3502943

Free space on /tmp= 66549 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-15/os-taillard-15-100-1.xml
COMMAND LINE= /tmp/evaluation/233618-1168327114/tramontane/bin/solver /tmp/evaluation/233618-1168327114/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node40/watcher-233618-1168327114 -o ROOT/results/node40/solver-233618-1168327114 -C 1800 -M 900  /tmp/evaluation/233618-1168327114/tramontane/bin/solver /tmp/evaluation/233618-1168327114/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  d022748892add36e7fd0a0a2d512e1b7

RANDOM SEED= 688853644

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.239
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.239
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        738472 kB
Buffers:         53436 kB
Cached:         440108 kB
SwapCached:          0 kB
Active:         785344 kB
Inactive:       451440 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        738472 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3388 kB
Writeback:           0 kB
Mapped:         763904 kB
Slab:            64456 kB
Committed_AS:  4753804 kB
PageTables:       3252 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66549 MiB



End job on node40 on Tue Jan  9 07:18:35 UTC 2007