Trace number 2116338

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
Choco2.1.1b 2009-07-16SAT 0.826874 0.895451

DiagnosticValue
CHECKS0
NODES43

General information on the benchmark

Namecsp/primes-10/
normalized-primes-10-40-2-3.xml
MD5SUM1866632d839b156c7c2250799bfd9750
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.014997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints40
Maximum constraint arity5
Maximum domain size28
Number of constraints which are defined in extension0
Number of constraints which are defined in intension40
Global constraints used (with number of constraints)

Solver Data 

0.77/0.83	s SATISFIABLE
0.77/0.83	v 3 17 26 13 2 13 20 7 22 3 5 19 2 17 7 21 27 10 5 19 3 14 21 20 24 23 12 7 28 4 15 5 2 23 29 12 29 11 12 5 24 27 7 13 21 3 21 11 4 26 29 17 3 8 22 6 9 6 3 3 13 13 19 19 16 10 14 17 7 16 11 15 2 13 9 19 2 2 29 2 18 23 16 16 3 20 2 5 21 29 3 29 11 2 24 10 22 17 11 29 
0.77/0.83	d AC 32
0.77/0.83	d RUNTIME 0.72
0.77/0.83	d NODES 43
0.77/0.83	d NODES/s 60
0.77/0.83	d BACKTRACKS 11
0.77/0.83	d BACKTRACKS/s 15
0.77/0.83	d CHECKS 0
0.77/0.83	d CHECKS/s 0
0.77/0.83	c SAT 0.72 TIME      43 NDS    273 PARSTIME      106 BUILDPB       165 CONFIG        176 RES       true RESTART       1 HEURISTIC       true RANDVAL

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2116338-1248030952/watcher-2116338-1248030952 -o /tmp/evaluation-result-2116338-1248030952/solver-2116338-1248030952 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file HOME/instance-2116338-1248030952.xml -randval true -h 1 -ac 32 -saclim 60 -s true -verb 0 -seed 11041979 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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


[startup+0 s]
/proc/loadavg: 2.08 2.02 1.93 4/80 23216
/proc/meminfo: memFree=807856/2055920 swapFree=4192812/4192956
[pid=23216] ppid=23214 vsize=18576 CPUtime=0
/proc/23216/stat : 23216 (runsolver) R 23214 23216 22036 0 -1 4194368 16 0 0 0 0 0 0 0 19 0 1 0 90158494 19021824 284 996147200 4194304 4302564 548682068272 18446744073709551615 251255123239 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/23216/statm: 4644 284 249 26 0 2626 0

[startup+0.0508229 s]
/proc/loadavg: 2.08 2.02 1.93 4/80 23216
/proc/meminfo: memFree=807856/2055920 swapFree=4192812/4192956
[pid=23216] ppid=23214 vsize=860216 CPUtime=0.03
/proc/23216/stat : 23216 (java) S 23214 23216 22036 0 -1 0 2389 0 1 0 2 1 0 0 18 0 6 0 90158494 880861184 1949 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800971 18446744073709551615 0 0 17 1 0 0
/proc/23216/statm: 215054 1949 907 9 0 209969 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 860216

[startup+0.101863 s]
/proc/loadavg: 2.08 2.02 1.93 4/80 23216
/proc/meminfo: memFree=807856/2055920 swapFree=4192812/4192956
[pid=23216] ppid=23214 vsize=864072 CPUtime=0.08
/proc/23216/stat : 23216 (java) S 23214 23216 22036 0 -1 0 3766 0 1 0 7 1 0 0 18 0 9 0 90158494 884809728 3231 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/23216/statm: 216018 3231 1698 9 0 210487 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 864072

[startup+0.301885 s]
/proc/loadavg: 2.08 2.02 1.93 4/80 23216
/proc/meminfo: memFree=807856/2055920 swapFree=4192812/4192956
[pid=23216] ppid=23214 vsize=864388 CPUtime=0.27
/proc/23216/stat : 23216 (java) S 23214 23216 22036 0 -1 0 4871 0 1 0 25 2 0 0 18 0 9 0 90158494 885133312 4287 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/23216/statm: 216097 4287 1883 9 0 210566 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 864388

[startup+0.701927 s]
/proc/loadavg: 2.08 2.02 1.93 4/80 23216
/proc/meminfo: memFree=807856/2055920 swapFree=4192812/4192956
[pid=23216] ppid=23214 vsize=864560 CPUtime=0.68
/proc/23216/stat : 23216 (java) S 23214 23216 22036 0 -1 0 7145 0 1 0 64 4 0 0 18 0 9 0 90158494 885309440 6525 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/23216/statm: 216140 6525 1967 9 0 210609 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 864560

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

[startup+0.801937 s]
/proc/loadavg: 2.08 2.02 1.93 4/80 23216
/proc/meminfo: memFree=807856/2055920 swapFree=4192812/4192956
[pid=23216] ppid=23214 vsize=864560 CPUtime=0.77
/proc/23216/stat : 23216 (java) S 23214 23216 22036 0 -1 0 7241 0 1 0 73 4 0 0 18 0 9 0 90158494 885309440 6621 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/23216/statm: 216140 6621 1967 9 0 210609 0
Current children cumulated CPU time (s) 0.77
Current children cumulated vsize (KiB) 864560

Child status: 0
Real time (s): 0.895451
CPU time (s): 0.826874
CPU user time (s): 0.774882
CPU system time (s): 0.051992
CPU usage (%): 92.3416
Max. virtual memory (cumulated for all children) (KiB): 864560

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

runsolver used 0.006998 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node64 at 2009-07-19 21:15:52
IDJOB=2116338
IDBENCH=56716
IDSOLVER=780
FILE ID=node64/2116338-1248030952
PBS_JOBID= 9528921
Free space on /tmp= 66368 MiB

SOLVER NAME= Choco2.1.1b 2009-07-16
BENCH NAME= CPAI08/csp/primes-10/normalized-primes-10-40-2-3.xml
COMMAND LINE= java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file BENCHNAME -randval true -h 1 -ac 32 -saclim 60 -s true -verb 0 -seed 11041979
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2116338-1248030952/watcher-2116338-1248030952 -o /tmp/evaluation-result-2116338-1248030952/solver-2116338-1248030952 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file HOME/instance-2116338-1248030952.xml -randval true -h 1 -ac 32 -saclim 60 -s true -verb 0 -seed 11041979

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 1866632d839b156c7c2250799bfd9750
RANDOM SEED=764749171

node64.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.220
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.220
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:        808400 kB
Buffers:        104276 kB
Cached:         945576 kB
SwapCached:          0 kB
Active:         431196 kB
Inactive:       721796 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        808400 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            5148 kB
Writeback:           0 kB
Mapped:         120996 kB
Slab:            79504 kB
Committed_AS:  1253760 kB
PageTables:       1960 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66364 MiB
End job on node64 at 2009-07-19 21:15:53