Trace number 234515

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
VALCSP 3.0SAT 1.56376 1.5797

DiagnosticValue
CHECKS26184400
NODES78

General information on the benchmark

Nametaillard/os-taillard-5/
os-taillard-5-105-1.xml
MD5SUM3aa724cf223b245dc8139479c90680a3
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.019996
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables25
Number of constraints100
Maximum constraint arity2
Maximum domain size275
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
Global constraints used (with number of constraints)

Solver Data (download as text)

1.57	s SATISFIABLE
1.57	v 90 215 183 0 253 90 215 112 141 0 112 0 245 86 238 87 120 0 245 205 86 141 183 0 253 
1.57	d CHECKS 2.61844e+07
1.57	d NODES 78
1.57

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/node2/watcher-234515-1168332583 -o ROOT/results/node2/solver-234515-1168332583 -C 1800 -M 900 /tmp/evaluation/234515-1168332583/VALCSP /tmp/evaluation/234515-1168332583/unknown.xml 

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.72 1.94 1.97 5/93 11559
/proc/meminfo: memFree=1253712/2055920 swapFree=4191880/4192956
[pid=11558] ppid=11556 vsize=2128 CPUtime=0.02
/proc/11558/stat : 11558 (VALCSP) R 11556 11558 10749 0 -1 4194304 277 0 0 0 2 0 0 0 19 0 1 0 181654115 2179072 255 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530258 0 0 4096 0 0 0 0 17 1 0 0
/proc/11558/statm: 532 255 64 8 0 204 0

[startup+0.132462 s]
/proc/loadavg: 1.72 1.94 1.97 5/93 11559
/proc/meminfo: memFree=1253712/2055920 swapFree=4191880/4192956
[pid=11558] ppid=11556 vsize=3448 CPUtime=0.12
/proc/11558/stat : 11558 (VALCSP) R 11556 11558 10749 0 -1 4194304 609 0 0 0 12 0 0 0 20 0 1 0 181654115 3530752 587 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530960 0 0 4096 0 0 0 0 17 1 0 0
/proc/11558/statm: 862 587 64 8 0 534 0
Current children cumulated CPU time (s) 0.12
Current children cumulated vsize (KiB) 3448

[startup+0.540497 s]
/proc/loadavg: 1.72 1.94 1.97 5/93 11559
/proc/meminfo: memFree=1253712/2055920 swapFree=4191880/4192956
[pid=11558] ppid=11556 vsize=10312 CPUtime=0.52
/proc/11558/stat : 11558 (VALCSP) R 11556 11558 10749 0 -1 4194304 2321 0 0 0 52 0 0 0 24 0 1 0 181654115 10559488 2299 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530220 0 0 4096 0 0 0 0 17 1 0 0
/proc/11558/statm: 2578 2299 64 8 0 2250 0
Current children cumulated CPU time (s) 0.52
Current children cumulated vsize (KiB) 10312

[startup+1.36165 s]
/proc/loadavg: 1.72 1.94 1.97 3/93 11559
/proc/meminfo: memFree=1236432/2055920 swapFree=4191880/4192956
[pid=11558] ppid=11556 vsize=22588 CPUtime=1.34
/proc/11558/stat : 11558 (VALCSP) R 11556 11558 10749 0 -1 4194304 5395 0 0 0 133 1 0 0 25 0 1 0 181654115 23130112 5373 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530955 0 0 4096 0 0 0 0 17 1 0 0
/proc/11558/statm: 5647 5373 64 8 0 5319 0
Current children cumulated CPU time (s) 1.34
Current children cumulated vsize (KiB) 22588

Child status: 0
Real time (s): 1.5797
CPU time (s): 1.56376
CPU user time (s): 1.54577
CPU system time (s): 0.017997
CPU usage (%): 98.9911
Max. virtual memory (cumulated for all children) (KiB): 22588

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

runsolver used 0.001999 s user time and 0.010998 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Tue Jan  9 08:49:43 UTC 2007


IDJOB= 234515
IDBENCH= 6693
FILE ID= node2/234515-1168332583

PBS_JOBID= 3503074

Free space on /tmp= 66534 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-5/os-taillard-5-105-1.xml
COMMAND LINE= /tmp/evaluation/234515-1168332583/VALCSP /tmp/evaluation/234515-1168332583/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-234515-1168332583 -o ROOT/results/node2/solver-234515-1168332583 -C 1800 -M 900  /tmp/evaluation/234515-1168332583/VALCSP /tmp/evaluation/234515-1168332583/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  3aa724cf223b245dc8139479c90680a3

RANDOM SEED= 364317557

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.259
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.259
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:       1254768 kB
Buffers:         74476 kB
Cached:         279240 kB
SwapCached:        292 kB
Active:         612900 kB
Inactive:       134492 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1254768 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             480 kB
Writeback:           0 kB
Mapped:         421952 kB
Slab:            37588 kB
Committed_AS:  5685940 kB
PageTables:       3080 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= 66534 MiB



End job on node2 on Tue Jan  9 08:49:46 UTC 2007