Trace number 2062192

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.1 2009-06-10SAT 0.858869 0.884668

DiagnosticValue
CHECKS0
NODES13

General information on the benchmark

Namecsp/allsquares/
normalized-squares-5-5.xml
MD5SUMbb9644ae85a99b575f97aaf4474e013c
Bench CategoryAlldiff+Cumul+Elt+WSum (alldiff,cumulative,element,weightedsum)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.026994
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints53
Maximum constraint arity5
Maximum domain size9
Number of constraints which are defined in extension0
Number of constraints which are defined in intension41
Global constraints used (with number of constraints)cumulative(2),weightedsum(10)

Solver Data 

0.79/0.85	s SATISFIABLE
0.79/0.85	v 6 6 1 5 0 3 1 5 5 0 0 0 0 1 0 1 1 0 0 0 1 0 0 1 0 0 0 1 1 0 0 0 1 0 0 1 0 0 1 0 0 0 0 0 0 1 0 1 0 1 
0.79/0.85	d AC 32
0.79/0.85	d RUNTIME 0.752
0.79/0.85	d NODES 13
0.79/0.85	d NODES/s 17
0.79/0.85	d BACKTRACKS 0
0.79/0.85	d BACKTRACKS/s 0
0.79/0.85	d CHECKS 0
0.79/0.85	d CHECKS/s 0
0.79/0.85	c SAT 0.752 TIME      13 NDS    225 PARSTIME      256 BUILDPB       271 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-2062192-1247328334/watcher-2062192-1247328334 -o /tmp/evaluation-result-2062192-1247328334/solver-2062192-1247328334 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2062192-1247328334.xml -h 1 -randval true -ac 32 -rest true -rb 10 -rg 1.3 -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.17 2.17 2.00 4/80 14696
/proc/meminfo: memFree=1069728/2055920 swapFree=4192956/4192956
[pid=14696] ppid=14694 vsize=152 CPUtime=0
/proc/14696/stat : 14696 (java) R 14694 14696 10539 0 -1 0 222 0 0 0 0 0 0 0 18 0 1 0 19900374 155648 26 996147200 134512640 134550932 4294955840 18446744073709551615 6926635 0 0 4096 0 0 0 0 17 0 0 0
/proc/14696/statm: 38 26 19 9 0 4 0

[startup+0.067339 s]
/proc/loadavg: 2.17 2.17 2.00 4/80 14696
/proc/meminfo: memFree=1069728/2055920 swapFree=4192956/4192956
[pid=14696] ppid=14694 vsize=862188 CPUtime=0.05
/proc/14696/stat : 14696 (java) S 14694 14696 10539 0 -1 0 3017 0 1 0 4 1 0 0 18 0 9 0 19900374 882880512 2498 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/14696/statm: 215547 2499 1196 9 0 210416 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 862188

[startup+0.101343 s]
/proc/loadavg: 2.17 2.17 2.00 4/80 14696
/proc/meminfo: memFree=1069728/2055920 swapFree=4192956/4192956
[pid=14696] ppid=14694 vsize=864096 CPUtime=0.09
/proc/14696/stat : 14696 (java) S 14694 14696 10539 0 -1 0 3895 0 1 0 7 2 0 0 18 0 9 0 19900374 884834304 3342 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/14696/statm: 216024 3342 1749 9 0 210492 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 864096

[startup+0.30138 s]
/proc/loadavg: 2.17 2.17 2.00 4/80 14696
/proc/meminfo: memFree=1069728/2055920 swapFree=4192956/4192956
[pid=14696] ppid=14694 vsize=864376 CPUtime=0.29
/proc/14696/stat : 14696 (java) S 14694 14696 10539 0 -1 0 4989 0 1 0 26 3 0 0 18 0 9 0 19900374 885121024 4405 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/14696/statm: 216094 4405 1882 9 0 210562 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 864376

[startup+0.70145 s]
/proc/loadavg: 2.17 2.17 2.00 4/80 14696
/proc/meminfo: memFree=1069728/2055920 swapFree=4192956/4192956
[pid=14696] ppid=14694 vsize=864560 CPUtime=0.69
/proc/14696/stat : 14696 (java) S 14694 14696 10539 0 -1 0 7238 0 1 0 64 5 0 0 18 0 9 0 19900374 885309440 6616 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/14696/statm: 216140 6616 1978 9 0 210608 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 864560

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

[startup+0.801466 s]
/proc/loadavg: 2.17 2.17 2.00 4/80 14696
/proc/meminfo: memFree=1069728/2055920 swapFree=4192956/4192956
[pid=14696] ppid=14694 vsize=864560 CPUtime=0.79
/proc/14696/stat : 14696 (java) S 14694 14696 10539 0 -1 0 7504 0 1 0 74 5 0 0 18 0 9 0 19900374 885309440 6882 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/14696/statm: 216140 6882 1978 9 0 210608 0
Current children cumulated CPU time (s) 0.79
Current children cumulated vsize (KiB) 864560

Child status: 0
Real time (s): 0.884668
CPU time (s): 0.858869
CPU user time (s): 0.799878
CPU system time (s): 0.058991
CPU usage (%): 97.0838
Max. virtual memory (cumulated for all children) (KiB): 864560

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.799878
system time used= 0.058991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7782
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= 920
involuntary context switches= 903

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node14 at 2009-07-11 18:05:34
IDJOB=2062192
IDBENCH=53877
IDSOLVER=737
FILE ID=node14/2062192-1247328334
PBS_JOBID= 9506599
Free space on /tmp= 66492 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/allsquares/normalized-squares-5-5.xml
COMMAND LINE= java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file BENCHNAME -h 1 -randval true -ac 32 -rest true -rb 10 -rg 1.3 -saclim 60 -s true -verb 0 -seed 11041979
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2062192-1247328334/watcher-2062192-1247328334 -o /tmp/evaluation-result-2062192-1247328334/solver-2062192-1247328334 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2062192-1247328334.xml -h 1 -randval true -ac 32 -rest true -rb 10 -rg 1.3 -saclim 60 -s true -verb 0 -seed 11041979

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

MD5SUM BENCH= bb9644ae85a99b575f97aaf4474e013c
RANDOM SEED=509425572

node14.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.265
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.265
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:       1070208 kB
Buffers:         63252 kB
Cached:         793004 kB
SwapCached:          0 kB
Active:         406488 kB
Inactive:       526280 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1070208 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            2536 kB
Writeback:           0 kB
Mapped:          94392 kB
Slab:            38096 kB
Committed_AS:   894464 kB
PageTables:       1980 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= 66492 MiB
End job on node14 at 2009-07-11 18:05:35