Trace number 235413

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.219965 0.228537

General information on the benchmark

Nametaillard/os-taillard-10/
os-taillard-10-100-9.xml
MD5SUM9a2ef65edf8fd30850593c0a23951dfa
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.219965
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size604
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.10	c 
0.10	c Parsing xml file
0.10	c 	domains...............    0
0.10	c 	variables.............    0
0.10	c 	predicates............    0
0.10	c 	constraints........... 0.06
0.10	c Allocating memory
0.10	c 
0.10	c time limit = -1
0.10	c heuristic = dom/wdeg
0.10	c restart policy = Geometric increment
0.10	c restart base = 666
0.10	c restart factor = 1.33
0.10	c 
0.10	c Solving
0.10	c
0.21	s SATISFIABLE
0.21	v 594 33 500 518 354 223 85 136 0 291 63 322 589 197 153 276 0 425 264 518 154 122 459 298 330 509 258 46 0 72 179 469 327 516 552 594 324 0 260 391 159 559 425 248 494 427 223 87 330 1 455 179 160 245 588 0 382 503 72 330 552 154 420 459 245 382 65 0 291 144 509 0 391 451 494 89 322 250 159 122 536 0 469 230 42 382 160 298 105 89 382 0 42 160 480 264 250 84 153 423
0.21	d          SAT      1270 BTS       0.1 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/node33/watcher-235413-1168337722 -o ROOT/results/node33/solver-235413-1168337722 -C 1800 -M 900 /tmp/evaluation/235413-1168337722/tramontane/bin/solver /tmp/evaluation/235413-1168337722/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: 1.95 2.07 1.71 5/81 30055
/proc/meminfo: memFree=1339536/2055920 swapFree=4192224/4192956
[pid=30054] ppid=30052 vsize=540 CPUtime=0
/proc/30054/stat : 30054 (solver) R 30052 30054 29347 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 182166147 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 10945316 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/30054/statm: 135 26 21 92 0 18 0

[startup+0.103714 s]
/proc/loadavg: 1.95 2.07 1.71 5/81 30055
/proc/meminfo: memFree=1339536/2055920 swapFree=4192224/4192956
[pid=30054] ppid=30052 vsize=11672 CPUtime=0.09
/proc/30054/stat : 30054 (solver) R 30052 30054 29347 0 -1 4194304 2008 0 0 0 8 1 0 0 19 0 1 0 182166147 11952128 1976 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 11380347 0 0 4096 0 0 0 0 17 1 0 0
/proc/30054/statm: 2918 1976 713 92 0 1262 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11672

Child status: 0
Real time (s): 0.228537
CPU time (s): 0.219965
CPU user time (s): 0.204968
CPU system time (s): 0.014997
CPU usage (%): 96.2492
Max. virtual memory (cumulated for all children) (KiB): 12748

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

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node33 on Tue Jan  9 10:15:23 UTC 2007


IDJOB= 235413
IDBENCH= 6768
FILE ID= node33/235413-1168337722

PBS_JOBID= 3503373

Free space on /tmp= 66561 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  9a2ef65edf8fd30850593c0a23951dfa

RANDOM SEED= 664149372

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.281
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.281
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:       1339952 kB
Buffers:         14184 kB
Cached:         488544 kB
SwapCached:        268 kB
Active:         236788 kB
Inactive:       427844 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1339952 kB
SwapTotal:     4192956 kB
SwapFree:      4192224 kB
Dirty:            3188 kB
Writeback:           0 kB
Mapped:         179380 kB
Slab:            36236 kB
Committed_AS:  3718224 kB
PageTables:       2124 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= 66561 MiB



End job on node33 on Tue Jan  9 10:15:23 UTC 2007