Trace number 1127783

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
Concrete + CSP4J - MCRW Engine 2008-05-30OPTIMUM 0.348946 0.394017

DiagnosticValue
CHECKS1854
NODES20

General information on the benchmark

Namemaxcsp/cnf/3-40-100-1000/
normalized-cnf-3-40-100-730629_ext.xml
MD5SUM5956c20ecdf7b3784a3f1f46a2773405
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of falsified constraints0
Best CPU time to get the best result obtained on this benchmark0.043992
Satisfiable
(Un)Satisfiability was proved
Number of variables40
Number of constraints100
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension100
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.30	c CPU-LOAD 0.12
0.00/0.30	c LOADED 40 V (2 E), 100 ExtensionConstraintGeneral, arity 3, 0.12 cpu
0.00/0.34	s SATISFIABLE
0.00/0.34	o 98
0.00/0.34	v 1 0 1 1 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 0 0 0 1 0 0 1 0 1 0 1 1 1 0 1 1 1 
0.00/0.34	o 99
0.00/0.34	v 1 0 1 1 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 1 0 1 0 1 1 1 0 1 1 1 
0.00/0.35	o 100
0.00/0.35	v 1 0 1 1 0 1 0 1 1 1 1 1 1 0 0 0 0 1 0 0 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 1 1 
0.00/0.35	s OPTIMUM FOUND
0.00/0.35	d NODES 20
0.00/0.35	d CHECKS 1854
0.00/0.35	c total-assgn: 20
0.00/0.35	c total-constraint-ccks: 1854
0.00/0.35	c total-constraint-presence-ccks: 251
0.00/0.35	c total-cpu: 0.02
0.00/0.35	c total-matrix2d-ccks: 0
0.00/0.35	c total-matrix2d-presence-ccks: 0
0.00/0.35	c tuples: 0
0.00/0.35	c tuples-collisions: 0
0.00/0.35	c TOTAL-NODES 20
0.00/0.35	c TOTAL-CPU 0.02

Verifier Data (download as text)

OK	0	100
0 unsatisfied constraints, 100 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-1127783-1216776025/watcher-1127783-1216776025 -o /tmp/evaluation-result-1127783-1216776025/solver-1127783-1216776025 -C 3600 -W 4000 -M 900 --output-limit 1,15 HOME/concrete.sh -c -ext 0 -s MCRW -max HOME/instance-1127783-1216776025.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.25 2.08 2.02 4/73 5956
/proc/meminfo: memFree=1273840/2055920 swapFree=4192956/4192956
[pid=5956] ppid=5954 vsize=5356 CPUtime=0
/proc/5956/stat : 5956 (concrete.sh) R 5954 5956 5467 0 -1 4194304 295 128 0 0 0 0 0 0 21 0 1 0 4693198 5484544 242 996147200 4194304 4889804 548682068752 18446744073709551615 240472783461 0 2147483391 4100 65536 0 0 0 17 1 0 0
/proc/5956/statm: 1339 242 201 169 0 50 0

[startup+0.06799 s]
/proc/loadavg: 2.25 2.08 2.02 4/73 5956
/proc/meminfo: memFree=1273840/2055920 swapFree=4192956/4192956
[pid=5956] ppid=5954 vsize=5356 CPUtime=0
/proc/5956/stat : 5956 (concrete.sh) S 5954 5956 5467 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 4693198 5484544 242 996147200 4194304 4889804 548682068752 18446744073709551615 240472613700 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/5956/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.101993 s]
/proc/loadavg: 2.25 2.08 2.02 4/73 5956
/proc/meminfo: memFree=1273840/2055920 swapFree=4192956/4192956
[pid=5956] ppid=5954 vsize=5356 CPUtime=0
/proc/5956/stat : 5956 (concrete.sh) S 5954 5956 5467 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 4693198 5484544 242 996147200 4194304 4889804 548682068752 18446744073709551615 240472613700 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/5956/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.302005 s]
/proc/loadavg: 2.25 2.08 2.02 4/73 5956
/proc/meminfo: memFree=1273840/2055920 swapFree=4192956/4192956
[pid=5956] ppid=5954 vsize=5356 CPUtime=0
/proc/5956/stat : 5956 (concrete.sh) S 5954 5956 5467 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 4693198 5484544 242 996147200 4194304 4889804 548682068752 18446744073709551615 240472613700 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/5956/statm: 1339 242 201 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.394017
CPU time (s): 0.348946
CPU user time (s): 0.306953
CPU system time (s): 0.041993
CPU usage (%): 88.5611
Max. virtual memory (cumulated for all children) (KiB): 5356

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.306953
system time used= 0.041993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5922
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 414
involuntary context switches= 319

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node15 at 2008-07-23 03:20:25
IDJOB=1127783
IDBENCH=63982
IDSOLVER=335
FILE ID=node15/1127783-1216776025
PBS_JOBID= 7974082
Free space on /tmp= 66552 MiB

SOLVER NAME= Concrete + CSP4J - MCRW Engine 2008-05-30
BENCH NAME= CPAI08/maxcsp/cnf/3-40-100-1000/normalized-cnf-3-40-100-730629_ext.xml
COMMAND LINE= HOME/concrete.sh -c -ext 0 -s MCRW -max BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1127783-1216776025/watcher-1127783-1216776025 -o /tmp/evaluation-result-1127783-1216776025/solver-1127783-1216776025 -C 3600 -W 4000 -M 900 --output-limit 1,15  HOME/concrete.sh -c -ext 0 -s MCRW -max HOME/instance-1127783-1216776025.xml 

TIME LIMIT= 3600 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 5956c20ecdf7b3784a3f1f46a2773405
RANDOM SEED=685335390

node15.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	: 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.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:       1274320 kB
Buffers:         42096 kB
Cached:         651504 kB
SwapCached:          0 kB
Active:         156788 kB
Inactive:       553752 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1274320 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             760 kB
Writeback:           0 kB
Mapped:          27948 kB
Slab:            56248 kB
Committed_AS:    81244 kB
PageTables:       1944 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= 66552 MiB
End job on node15 at 2008-07-23 03:20:25