Trace number 1115150

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 NameAnswerNumber of falsified constraintsCPU timeWall clock time
toulbar2 2008-06-27OPTIMUM2 0.176972 0.193573

General information on the benchmark

Namecsp/composed-75-1-80/
normalized-composed-75-1-80-1_ext.xml
MD5SUM48585bc76f56f4e7178f9d3982b8e6f7
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of falsified constraints2
Best CPU time to get the best result obtained on this benchmark0.176972
Satisfiable
(Un)Satisfiability was proved
Number of variables83
Number of constraints702
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension702
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00/0.07	o 8
0.00/0.07	o 7
0.00/0.08	o 6
0.00/0.09	o 5
0.00/0.09	o 4
0.00/0.12	o 3
0.00/0.14	o 2
0.00/0.19	s OPTIMUM FOUND
0.00/0.19	v 0 8 2 0 3 2 5 4 2 0 5 2 1 2 6 4 1 1 4 8 6 0 0 5 3 0 4 1 3 3 2 2 9 0 4 2 0 0 2 4 0 6 3 0 4 7 0 1 1 0 1 3 4 3 3 1 0 4 5 0 1 5 2 0 3 6 0 2 0 5 5 4 8 0 0 7 3 4 9 3 2 5 7

Verifier Data (download as text)

OK	2	700
2 unsatisfied constraints, 700 satisfied constraints

Watcher Data (download as text)

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

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1115150-1215915587/watcher-1115150-1215915587 -o /tmp/evaluation-result-1115150-1215915587/solver-1115150-1215915587 -C 3600 -W 4000 -M 900 --output-limit 1,15 HOME/solver.sh HOME/instance-1115150-1215915587.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 3630 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 4000 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.69 2.73 2.65 5/240 24121
/proc/meminfo: memFree=1676760/2055920 swapFree=4192812/4192956
[pid=24121] ppid=24119 vsize=18572 CPUtime=0
/proc/24121/stat : 24121 (runsolver) R 24119 24121 22121 0 -1 4194368 15 0 0 0 0 0 0 0 19 0 1 0 48255656 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 251279240487 0 0 4096 24578 0 0 0 17 1 0 0
/proc/24121/statm: 4643 292 257 25 0 2626 0

[startup+0.095162 s]
/proc/loadavg: 2.69 2.73 2.65 5/240 24121
/proc/meminfo: memFree=1676760/2055920 swapFree=4192812/4192956
[pid=24121] ppid=24119 vsize=5356 CPUtime=0
/proc/24121/stat : 24121 (solver.sh) S 24119 24121 22121 0 -1 4194304 302 117 0 0 0 0 0 0 19 0 1 0 48255656 5484544 231 996147200 4194304 4889804 548682068832 18446744073709551615 251279237956 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/24121/statm: 1339 231 192 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.101161 s]
/proc/loadavg: 2.69 2.73 2.65 5/240 24121
/proc/meminfo: memFree=1676760/2055920 swapFree=4192812/4192956
[pid=24121] ppid=24119 vsize=5356 CPUtime=0
/proc/24121/stat : 24121 (solver.sh) S 24119 24121 22121 0 -1 4194304 302 117 0 0 0 0 0 0 19 0 1 0 48255656 5484544 231 996147200 4194304 4889804 548682068832 18446744073709551615 251279237956 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/24121/statm: 1339 231 192 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

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

Child status: 0
Real time (s): 0.193573
CPU time (s): 0.176972
CPU user time (s): 0.167974
CPU system time (s): 0.008998
CPU usage (%): 91.4239
Max. virtual memory (cumulated for all children) (KiB): 5356

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

runsolver used 0.002999 second user time and 0.016997 second system time

The end

Launcher Data (download as text)

Begin job on node92 at 2008-07-13 04:19:47
IDJOB=1115150
IDBENCH=61822
IDSOLVER=371
FILE ID=node92/1115150-1215915587
PBS_JOBID= 7903698
Free space on /tmp= 66476 MiB

SOLVER NAME= toulbar2 2008-06-27
BENCH NAME= CPAI08/csp/composed-75-1-80/normalized-composed-75-1-80-1_ext.xml
COMMAND LINE= HOME/solver.sh BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1115150-1215915587/watcher-1115150-1215915587 -o /tmp/evaluation-result-1115150-1215915587/solver-1115150-1215915587 -C 3600 -W 4000 -M 900 --output-limit 1,15  HOME/solver.sh HOME/instance-1115150-1215915587.xml 

TIME LIMIT= 3600 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 48585bc76f56f4e7178f9d3982b8e6f7
RANDOM SEED=388611574

node92.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.236
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.236
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1677240 kB
Buffers:         18932 kB
Cached:          99184 kB
SwapCached:          0 kB
Active:         260148 kB
Inactive:        50512 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1677240 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            9560 kB
Writeback:           0 kB
Mapped:         214352 kB
Slab:            38900 kB
Committed_AS:  1277676 kB
PageTables:      11700 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= 66468 MiB
End job on node92 at 2008-07-13 04:19:47