Trace number 235490

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
Mistral 2006-12-04SAT 0.155976 0.167209

General information on the benchmark

Nametaillard/os-taillard-10/
os-taillard-10-105-9.xml
MD5SUMbe590f06412d1b3dfd8fcbccbb49df5a
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.152976
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size634
Number of constraints which are defined in extension0
Number of constraints which are defined in intension900
Global constraints used (with number of constraints)

Solver Data (download as text)

0.02	c 
0.02	c Parsing xml file
0.02	c 	domains...............    0
0.02	c 	variables.............    0
0.02	c 	predicates............    0
0.02	c 	constraints........... 0.06
0.09	c Allocating memory
0.09	c 
0.09	c time limit = -1
0.09	c heuristic = dom/wdeg
0.09	c restart policy = No restart
0.09	c 
0.09	c Solving
0.09	c
0.15	s SATISFIABLE
0.15	v 569 464 559 188 400 265 344 0 264 166 57 382 2 315 147 11 269 518 487 191 196 302 0 561 459 50 593 170 123 156 499 432 410 2 593 0 311 337 524 88 525 589 524 260 459 392 200 372 93 0 589 525 480 391 271 171 300 249 0 147 328 2 581 468 410 372 249 184 93 0 487 400 340 311 302 269 200 128 37 0 563 535 468 400 344 260 190 106 53 37 518 476 379 315 180 146 136 69 50 0
0.15	d          SAT       292 BTS      0.04 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/node38/watcher-235490-1168338084 -o ROOT/results/node38/solver-235490-1168338084 -C 1800 -M 900 /tmp/evaluation/235490-1168338084/mistral/bin/solver /tmp/evaluation/235490-1168338084/unknown.xml -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: 1.91 1.97 1.93 5/81 8924
/proc/meminfo: memFree=1376048/2055920 swapFree=4192812/4192956
[pid=8923] ppid=8921 vsize=540 CPUtime=0
/proc/8923/stat : 8923 (solver) R 8921 8923 7375 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 182208068 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8606500 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/8923/statm: 135 26 21 92 0 18 0

[startup+0.104265 s]
/proc/loadavg: 1.91 1.97 1.93 5/81 8924
/proc/meminfo: memFree=1376048/2055920 swapFree=4192812/4192956
[pid=8923] ppid=8921 vsize=10620 CPUtime=0.08
/proc/8923/stat : 8923 (solver) R 8921 8923 7375 0 -1 4194304 1731 0 0 0 8 0 0 0 20 0 1 0 182208068 10874880 1699 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 9898513 0 0 4096 0 0 0 0 17 1 0 0
/proc/8923/statm: 2655 1699 711 92 0 999 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 10620

Child status: 0
Real time (s): 0.167209
CPU time (s): 0.155976
CPU user time (s): 0.143978
CPU system time (s): 0.011998
CPU usage (%): 93.282
Max. virtual memory (cumulated for all children) (KiB): 10620

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.143978
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2422
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= 64

runsolver used 0.004999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Tue Jan  9 10:21:24 UTC 2007


IDJOB= 235490
IDBENCH= 6773
FILE ID= node38/235490-1168338084

PBS_JOBID= 3503363

Free space on /tmp= 66519 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-10/os-taillard-10-105-9.xml
COMMAND LINE= /tmp/evaluation/235490-1168338084/mistral/bin/solver /tmp/evaluation/235490-1168338084/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-235490-1168338084 -o ROOT/results/node38/solver-235490-1168338084 -C 1800 -M 900  /tmp/evaluation/235490-1168338084/mistral/bin/solver /tmp/evaluation/235490-1168338084/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  be590f06412d1b3dfd8fcbccbb49df5a

RANDOM SEED= 322098807

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.267
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.267
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:       1376464 kB
Buffers:         11848 kB
Cached:         479316 kB
SwapCached:          0 kB
Active:         198364 kB
Inactive:       428384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1376464 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3064 kB
Writeback:           0 kB
Mapped:         153640 kB
Slab:            37676 kB
Committed_AS:  4306452 kB
PageTables:       2160 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= 66519 MiB



End job on node38 on Tue Jan  9 10:21:24 UTC 2007