Trace number 2115195

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.814875 0.840541

DiagnosticValue
CHECKS0
NODES9

General information on the benchmark

Namecsp/primes-30/
normalized-primes-30-60-2-5.xml
MD5SUM175eb2ae2b98149203997bb89fdddaa2
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.025995
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints60
Maximum constraint arity7
Maximum domain size112
Number of constraints which are defined in extension0
Number of constraints which are defined in intension60
Global constraints used (with number of constraints)

Solver Data 

0.78/0.82	s SATISFIABLE
0.78/0.82	v 43 111 107 16 13 101 59 41 29 3 5 19 73 71 89 59 2 17 83 59 37 23 95 10 5 73 5 43 19 101 113 41 41 67 113 107 43 59 3 83 29 7 79 113 47 8 23 47 13 2 89 59 7 73 103 7 5 73 59 3 53 53 47 107 103 13 59 29 43 61 97 53 41 4 47 107 47 87 7 73 19 67 17 23 23 97 7 37 47 71 41 2 103 67 71 83 59 17 97 113 
0.78/0.82	d AC 32
0.78/0.82	d RUNTIME 0.709
0.78/0.82	d NODES 9
0.78/0.82	d NODES/s 13
0.78/0.82	d BACKTRACKS 0
0.78/0.82	d BACKTRACKS/s 0
0.78/0.82	d CHECKS 0
0.78/0.82	d CHECKS/s 0
0.78/0.82	c SAT 0.709 TIME      9 NDS    322 PARSTIME      118 BUILDPB       171 CONFIG        98 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-2115195-1248028474/watcher-2115195-1248028474 -o /tmp/evaluation-result-2115195-1248028474/solver-2115195-1248028474 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file HOME/instance-2115195-1248028474.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.29 2.15 1.84 4/80 572
/proc/meminfo: memFree=1054112/2055920 swapFree=4191900/4192956
[pid=572] ppid=570 vsize=18576 CPUtime=0
/proc/572/stat : 572 (runsolver) R 570 572 32666 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 89914047 19021824 284 996147200 4194304 4302564 548682068272 18446744073709551615 217871609127 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/572/statm: 4644 284 249 26 0 2626 0

[startup+0.080844 s]
/proc/loadavg: 2.29 2.15 1.84 4/80 572
/proc/meminfo: memFree=1054112/2055920 swapFree=4191900/4192956
[pid=572] ppid=570 vsize=862284 CPUtime=0.06
/proc/572/stat : 572 (java) S 570 572 32666 0 -1 0 3223 0 1 0 5 1 0 0 18 0 9 0 89914047 882978816 2691 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/572/statm: 215571 2691 1294 9 0 210441 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 862284

[startup+0.101848 s]
/proc/loadavg: 2.29 2.15 1.84 4/80 572
/proc/meminfo: memFree=1054112/2055920 swapFree=4191900/4192956
[pid=572] ppid=570 vsize=864092 CPUtime=0.08
/proc/572/stat : 572 (java) S 570 572 32666 0 -1 0 3813 0 1 0 7 1 0 0 18 0 9 0 89914047 884830208 3276 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/572/statm: 216023 3276 1724 9 0 210492 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 864092

[startup+0.301869 s]
/proc/loadavg: 2.29 2.15 1.84 4/80 572
/proc/meminfo: memFree=1054112/2055920 swapFree=4191900/4192956
[pid=572] ppid=570 vsize=864832 CPUtime=0.28
/proc/572/stat : 572 (java) S 570 572 32666 0 -1 0 4879 0 1 0 26 2 0 0 18 0 9 0 89914047 885587968 4295 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/572/statm: 216208 4295 1884 9 0 210677 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 864832

[startup+0.701914 s]
/proc/loadavg: 2.29 2.15 1.84 4/80 572
/proc/meminfo: memFree=1054112/2055920 swapFree=4191900/4192956
[pid=572] ppid=570 vsize=865068 CPUtime=0.67
/proc/572/stat : 572 (java) S 570 572 32666 0 -1 0 7558 0 1 0 63 4 0 0 18 0 9 0 89914047 885829632 6939 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/572/statm: 216267 6939 1967 9 0 210736 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 865068

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

[startup+0.801924 s]
/proc/loadavg: 2.29 2.15 1.84 4/80 572
/proc/meminfo: memFree=1054112/2055920 swapFree=4191900/4192956
[pid=572] ppid=570 vsize=865068 CPUtime=0.78
/proc/572/stat : 572 (java) S 570 572 32666 0 -1 0 7703 0 1 0 73 5 0 0 18 0 9 0 89914047 885829632 7083 996147200 134512640 134550932 4294955888 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/572/statm: 216267 7083 1969 9 0 210736 0
Current children cumulated CPU time (s) 0.78
Current children cumulated vsize (KiB) 865068

Child status: 0
Real time (s): 0.840541
CPU time (s): 0.814875
CPU user time (s): 0.756884
CPU system time (s): 0.057991
CPU usage (%): 96.9465
Max. virtual memory (cumulated for all children) (KiB): 865068

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.756884
system time used= 0.057991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7869
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= 673
involuntary context switches= 665

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node28 at 2009-07-19 20:34:34
IDJOB=2115195
IDBENCH=54372
IDSOLVER=780
FILE ID=node28/2115195-1248028474
PBS_JOBID= 9528991
Free space on /tmp= 66052 MiB

SOLVER NAME= Choco2.1.1b 2009-07-16
BENCH NAME= CPAI08/csp/primes-30/normalized-primes-30-60-2-5.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-2115195-1248028474/watcher-2115195-1248028474 -o /tmp/evaluation-result-2115195-1248028474/solver-2115195-1248028474 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco2.1.1.b.jar -file HOME/instance-2115195-1248028474.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= 175eb2ae2b98149203997bb89fdddaa2
RANDOM SEED=203301303

node28.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.230
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.230
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:       1054656 kB
Buffers:         64524 kB
Cached:         689756 kB
SwapCached:        384 kB
Active:         298508 kB
Inactive:       616012 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1054656 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            5296 kB
Writeback:           0 kB
Mapped:         176860 kB
Slab:            71516 kB
Committed_AS:  1337732 kB
PageTables:       2116 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= 66048 MiB
End job on node28 at 2009-07-19 20:34:35