Trace number 2116315

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.930858 0.952601

DiagnosticValue
CHECKS0
NODES303

General information on the benchmark

Namecsp/primes-15/
normalized-primes-15-20-3-7.xml
MD5SUM5a9755a4ca72128afdbeb99b36b30378
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.044992
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity10
Maximum domain size46
Number of constraints which are defined in extension0
Number of constraints which are defined in intension20
Global constraints used (with number of constraints)

Solver Data

0.89/0.93	s SATISFIABLE
0.89/0.93	v 17 38 43 12 11 38 19 12 18 45 46 20 9 11 12 40 21 29 2 39 43 39 30 47 7 44 8 47 35 25 26 37 43 12 4 39 28 3 46 45 19 20 16 16 38 24 11 7 28 2 8 43 6 43 32 10 28 22 46 3 13 7 25 47 30 17 44 47 36 8 16 37 34 7 36 23 17 32 20 11 33 13 12 47 25 17 11 43 46 3 45 37 27 33 29 24 11 29 34 47 
0.89/0.93	d AC 32
0.89/0.93	d RUNTIME 0.826
0.89/0.93	d NODES 303
0.89/0.93	d NODES/s 367
0.89/0.93	d BACKTRACKS 633
0.89/0.93	d BACKTRACKS/s 766
0.89/0.93	d CHECKS 0
0.89/0.93	d CHECKS/s 0
0.89/0.93	c SAT 0.826 TIME      303 NDS    268 PARSTIME      132 BUILDPB       152 CONFIG        274 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-2116315-1248030936/watcher-2116315-1248030936 -o /tmp/evaluation-result-2116315-1248030936/solver-2116315-1248030936 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file HOME/instance-2116315-1248030936.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.05 2.10 1.99 4/81 26970
/proc/meminfo: memFree=837056/2055920 swapFree=4191900/4192956
[pid=26970] ppid=26968 vsize=0 CPUtime=0
/proc/26970/stat : 26970 (java) R 26968 26970 25698 0 -1 0 197 0 0 0 0 0 0 0 21 0 1 0 90158975 0 0 996147200 0 0 0 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 0 0 0
/proc/26970/statm: 0 0 0 0 0 0 0

[startup+0.0851619 s]
/proc/loadavg: 2.05 2.10 1.99 4/81 26970
/proc/meminfo: memFree=837056/2055920 swapFree=4191900/4192956
[pid=26970] ppid=26968 vsize=862252 CPUtime=0.07
/proc/26970/stat : 26970 (java) S 26968 26970 25698 0 -1 0 3314 0 1 0 6 1 0 0 18 0 9 0 90158975 882946048 2782 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/26970/statm: 215563 2782 1309 9 0 210433 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 862252

[startup+0.10116 s]
/proc/loadavg: 2.05 2.10 1.99 4/81 26970
/proc/meminfo: memFree=837056/2055920 swapFree=4191900/4192956
[pid=26970] ppid=26968 vsize=864060 CPUtime=0.08
/proc/26970/stat : 26970 (java) S 26968 26970 25698 0 -1 0 3894 0 1 0 7 1 0 0 18 0 9 0 90158975 884797440 3341 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/26970/statm: 216015 3341 1747 9 0 210484 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 864060

[startup+0.301197 s]
/proc/loadavg: 2.05 2.10 1.99 4/81 26970
/proc/meminfo: memFree=837056/2055920 swapFree=4191900/4192956
[pid=26970] ppid=26968 vsize=864184 CPUtime=0.28
/proc/26970/stat : 26970 (java) S 26968 26970 25698 0 -1 0 4901 0 1 0 26 2 0 0 18 0 9 0 90158975 884924416 4317 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/26970/statm: 216046 4317 1883 9 0 210515 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 864184

[startup+0.701278 s]
/proc/loadavg: 2.05 2.10 1.99 4/81 26970
/proc/meminfo: memFree=837056/2055920 swapFree=4191900/4192956
[pid=26970] ppid=26968 vsize=864564 CPUtime=0.69
/proc/26970/stat : 26970 (java) S 26968 26970 25698 0 -1 0 7138 0 1 0 65 4 0 0 18 0 9 0 90158975 885313536 6518 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/26970/statm: 216141 6518 1965 9 0 210610 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 864564

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

[startup+0.901303 s]
/proc/loadavg: 2.05 2.10 1.99 4/81 26970
/proc/meminfo: memFree=837056/2055920 swapFree=4191900/4192956
[pid=26970] ppid=26968 vsize=864564 CPUtime=0.89
/proc/26970/stat : 26970 (java) S 26968 26970 25698 0 -1 0 7380 0 1 0 84 5 0 0 18 0 9 0 90158975 885313536 6760 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/26970/statm: 216141 6760 1969 9 0 210610 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 864564

Child status: 0
Real time (s): 0.952601
CPU time (s): 0.930858
CPU user time (s): 0.873867
CPU system time (s): 0.056991
CPU usage (%): 97.7175
Max. virtual memory (cumulated for all children) (KiB): 864564

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

runsolver used 0.007998 second user time and 0.004999 second system time

The end

Launcher Data

Begin job on node84 at 2009-07-19 21:15:36
IDJOB=2116315
IDBENCH=56682
IDSOLVER=780
FILE ID=node84/2116315-1248030936
PBS_JOBID= 9528888
Free space on /tmp= 66148 MiB

SOLVER NAME= Choco2.1.1b 2009-07-16
BENCH NAME= CPAI08/csp/primes-15/normalized-primes-15-20-3-7.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-2116315-1248030936/watcher-2116315-1248030936 -o /tmp/evaluation-result-2116315-1248030936/solver-2116315-1248030936 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file HOME/instance-2116315-1248030936.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= 5a9755a4ca72128afdbeb99b36b30378
RANDOM SEED=82529472

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        837536 kB
Buffers:         66068 kB
Cached:         946204 kB
SwapCached:        384 kB
Active:         256468 kB
Inactive:       871392 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        837536 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            5168 kB
Writeback:           0 kB
Mapped:         132020 kB
Slab:            75628 kB
Committed_AS:  1252176 kB
PageTables:       1952 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= 66144 MiB
End job on node84 at 2009-07-19 21:15:37