Trace number 2065793

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
Mistral 1.545SAT 0.300953 0.303455

DiagnosticValue
ASSIGNMENTS222
CHECKS242144
NODES222

General information on the benchmark

Namecsp/os-taillard-15/
normalized-os-taillard-15-100-2.xml
MD5SUMe37c7fc937e58b291ac15eb0bfb94ef9
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.300953
Satisfiable
(Un)Satisfiability was proved
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size899
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 

0.00/0.00	c mistral version 1.545
0.19/0.25	s SATISFIABLE
0.19/0.25	v 375 693 569 601 166 830 397 434 0 96 748 561 507 230 315 618 562 775 511 302 341 104 847 810 45 173 387 239 475 724 471 166 192 554 321 810 38 621 1 514 720 399 257 76 622 0 422 338 775 880 79 315 237 646 172 664 830 518 612 400 348 0 416 506 397 99 172 295 545 488 713 644 237 804 588 275 33 804 400 367 764 571 111 681 647 470 493 788 11 188 64 480 517 740 1 598 471 678 171 348 430 666 294 612 810 825 241 508 410 719 498 70 399 624 367 156 309 0 658 127 44 538 387 316 0 79 502 335 369 230 166 764 636 824 433 739 824 64 416 664 263 455 554 0 827 603 367 317 99 69 14 571 96 160 835 701 348 180 719 428 765 502 243 275 786 715 192 410 91 295 748 804 614 391 544 664 0 110 335 573 554 538 649 45 719 0 599 650 440 110 813 618 149 507 466 772 329 886 738 561 639 237 186 486 679 13 392 420 99 810 606 160 424 303 70 363 171 740 513 569 813 890 0 190 701
0.19/0.25	d CHECKS 242144
0.19/0.25	d ASSIGNMENTS 222
0.19/0.25	d NODES 222 BACKTRACKS 5 FAILURES 5 RUNTIME 0.06 TOTALTIME 0.24 NODES/s 3700 CHECKS/s 4.03573e+06

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2065793-1247339120/watcher-2065793-1247339120 -o /tmp/evaluation-result-2065793-1247339120/solver-2065793-1247339120 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2065793-1247339120.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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


[startup+0 s]
/proc/loadavg: 2.38 2.21 2.12 4/74 14459
/proc/meminfo: memFree=1839496/2055920 swapFree=4192812/4192956
[pid=14459] ppid=14457 vsize=4804 CPUtime=0
/proc/14459/stat : 14459 (ld-linux.so.2) R 14457 14459 14081 0 -1 4194304 182 0 0 0 0 0 0 0 18 0 1 0 20978145 4919296 163 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448480482 0 0 4096 0 0 0 0 17 0 0 0
/proc/14459/statm: 1201 163 138 29 0 16 0

[startup+0.0524331 s]
/proc/loadavg: 2.38 2.21 2.12 4/74 14459
/proc/meminfo: memFree=1839496/2055920 swapFree=4192812/4192956
[pid=14459] ppid=14457 vsize=6644 CPUtime=0.04
/proc/14459/stat : 14459 (ld-linux.so.2) R 14457 14459 14081 0 -1 4194304 867 0 0 0 4 0 0 0 18 0 1 0 20978145 6803456 846 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157381179 0 0 4096 0 0 0 0 17 0 0 0
/proc/14459/statm: 1661 847 378 29 0 476 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 6644

[startup+0.102435 s]
/proc/loadavg: 2.38 2.21 2.12 4/74 14459
/proc/meminfo: memFree=1839496/2055920 swapFree=4192812/4192956
[pid=14459] ppid=14457 vsize=7696 CPUtime=0.09
/proc/14459/stat : 14459 (ld-linux.so.2) R 14457 14459 14081 0 -1 4194304 1152 0 0 0 9 0 0 0 18 0 1 0 20978145 7880704 1131 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157381179 0 0 4096 0 0 0 0 17 0 0 0
/proc/14459/statm: 1924 1132 378 29 0 739 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7696

[startup+0.302455 s]
/proc/loadavg: 2.38 2.21 2.12 4/74 14459
/proc/meminfo: memFree=1839496/2055920 swapFree=4192812/4192956
[pid=14459] ppid=14457 vsize=0 CPUtime=0.28
/proc/14459/stat : 14459 (ld-linux.so.2) R 14457 14459 14081 0 -1 4194308 3229 0 0 0 27 1 0 0 19 0 1 0 20978145 0 0 996147200 0 0 0 0 0 0 0 4096 0 0 0 0 17 0 0 0
/proc/14459/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 0

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.303455
CPU time (s): 0.300953
CPU user time (s): 0.279957
CPU system time (s): 0.020996
CPU usage (%): 99.1755
Max. virtual memory (cumulated for all children) (KiB): 15324

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.279957
system time used= 0.020996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3229
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= 24
involuntary context switches= 9

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node31 at 2009-07-11 21:05:20
IDJOB=2065793
IDBENCH=54422
IDSOLVER=769
FILE ID=node31/2065793-1247339120
PBS_JOBID= 9506774
Free space on /tmp= 66348 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/os-taillard-15/normalized-os-taillard-15-100-2.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2065793-1247339120/watcher-2065793-1247339120 -o /tmp/evaluation-result-2065793-1247339120/solver-2065793-1247339120 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2065793-1247339120.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= e37c7fc937e58b291ac15eb0bfb94ef9
RANDOM SEED=1007486031

node31.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.216
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	: 5931.00
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.216
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:       1840040 kB
Buffers:          5076 kB
Cached:          81964 kB
SwapCached:          0 kB
Active:         133232 kB
Inactive:        31720 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1840040 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            8488 kB
Writeback:           0 kB
Mapped:          89116 kB
Slab:            35904 kB
Committed_AS:   194064 kB
PageTables:       2056 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66348 MiB
End job on node31 at 2009-07-11 21:05:21