Trace number 2062995

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.882865 0.913698

DiagnosticValue
CHECKS0
NODES151

General information on the benchmark

Namecsp/jnhSat/
normalized-jnh17_ext.xml
MD5SUM14fc882a70b97c9c8d63b0b73526ea96
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.030994
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints847
Maximum constraint arity11
Maximum domain size2
Number of constraints which are defined in extension847
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.78/0.89	s SATISFIABLE
0.78/0.89	v 0 1 1 0 0 1 0 1 0 0 1 0 0 0 0 0 1 1 1 1 1 0 0 0 0 1 1 0 1 1 0 0 1 0 1 0 0 1 1 1 0 1 1 1 1 1 1 1 1 0 0 1 1 0 1 1 1 0 1 1 1 0 1 0 1 1 0 1 1 1 1 0 1 1 1 0 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 1 0 1 1 1 0 1 
0.78/0.89	d AC 32
0.78/0.89	d RUNTIME 0.776
0.78/0.89	d NODES 151
0.78/0.89	d NODES/s 195
0.78/0.89	d BACKTRACKS 132
0.78/0.89	d BACKTRACKS/s 170
0.78/0.89	d CHECKS 0
0.78/0.89	d CHECKS/s 0
0.78/0.89	c SAT 0.776 TIME      151 NDS    337 PARSTIME      311 BUILDPB       128 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-2062995-1247329949/watcher-2062995-1247329949 -o /tmp/evaluation-result-2062995-1247329949/solver-2062995-1247329949 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2062995-1247329949.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.07 1.99 1.98 3/74 12669
/proc/meminfo: memFree=1088880/2055920 swapFree=4192956/4192956
[pid=12669] ppid=12667 vsize=18576 CPUtime=0
/proc/12669/stat : 12669 (runsolver) R 12667 12669 11026 0 -1 4194368 16 0 0 0 0 0 0 0 19 0 1 0 20058402 19021824 284 996147200 4194304 4302564 548682068192 18446744073709551615 235371293991 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/12669/statm: 4644 284 249 26 0 2626 0

[startup+0.045541 s]
/proc/loadavg: 2.07 1.99 1.98 3/74 12669
/proc/meminfo: memFree=1088880/2055920 swapFree=4192956/4192956
[pid=12669] ppid=12667 vsize=859892 CPUtime=0.02
/proc/12669/stat : 12669 (java) S 12667 12669 11026 0 -1 0 2290 0 1 0 1 1 0 0 18 0 5 0 20058402 880529408 1872 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800971 18446744073709551615 0 0 17 1 0 0
/proc/12669/statm: 215054 1951 907 9 0 209969 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 859892

[startup+0.107765 s]
/proc/loadavg: 2.07 1.99 1.98 3/74 12669
/proc/meminfo: memFree=1088880/2055920 swapFree=4192956/4192956
[pid=12669] ppid=12667 vsize=864064 CPUtime=0.09
/proc/12669/stat : 12669 (java) S 12667 12669 11026 0 -1 0 3869 0 1 0 7 2 0 0 18 0 9 0 20058402 884801536 3319 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/12669/statm: 216016 3319 1745 9 0 210484 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 864064

[startup+0.30178 s]
/proc/loadavg: 2.07 1.99 1.98 3/74 12669
/proc/meminfo: memFree=1088880/2055920 swapFree=4192956/4192956
[pid=12669] ppid=12667 vsize=864936 CPUtime=0.28
/proc/12669/stat : 12669 (java) S 12667 12669 11026 0 -1 0 4815 0 1 0 25 3 0 0 18 0 9 0 20058402 885694464 4237 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/12669/statm: 216234 4237 1863 9 0 210702 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 864936

[startup+0.701817 s]
/proc/loadavg: 2.07 1.99 1.98 3/74 12669
/proc/meminfo: memFree=1088880/2055920 swapFree=4192956/4192956
[pid=12669] ppid=12667 vsize=865056 CPUtime=0.68
/proc/12669/stat : 12669 (java) S 12667 12669 11026 0 -1 0 6838 0 1 0 63 5 0 0 18 0 9 0 20058402 885817344 6223 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/12669/statm: 216264 6223 1959 9 0 210732 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 865056

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

[startup+0.901831 s]
/proc/loadavg: 2.07 1.99 1.98 3/74 12669
/proc/meminfo: memFree=1088880/2055920 swapFree=4192956/4192956
[pid=12669] ppid=12667 vsize=865504 CPUtime=0.86
/proc/12669/stat : 12669 (java) S 12667 12669 11026 0 -1 0 7593 0 1 0 81 5 0 0 18 0 9 0 20058402 886276096 6976 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/12669/statm: 216376 6976 1970 9 0 210844 0
Current children cumulated CPU time (s) 0.86
Current children cumulated vsize (KiB) 865504

Child status: 0
Real time (s): 0.913698
CPU time (s): 0.882865
CPU user time (s): 0.819875
CPU system time (s): 0.06299
CPU usage (%): 96.6255
Max. virtual memory (cumulated for all children) (KiB): 865504

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.819875
system time used= 0.06299
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7597
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= 1106
involuntary context switches= 1080

runsolver used 0.006998 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node51 at 2009-07-11 18:32:29
IDJOB=2062995
IDBENCH=53950
IDSOLVER=737
FILE ID=node51/2062995-1247329949
PBS_JOBID= 9506527
Free space on /tmp= 66172 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/jnhSat/normalized-jnh17_ext.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-2062995-1247329949/watcher-2062995-1247329949 -o /tmp/evaluation-result-2062995-1247329949/solver-2062995-1247329949 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2062995-1247329949.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= 14fc882a70b97c9c8d63b0b73526ea96
RANDOM SEED=270684286

node51.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.225
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.225
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:       1089360 kB
Buffers:         60488 kB
Cached:         824804 kB
SwapCached:          0 kB
Active:         143828 kB
Inactive:       770964 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1089360 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            3068 kB
Writeback:           0 kB
Mapped:          40296 kB
Slab:            37012 kB
Committed_AS:   223028 kB
PageTables:       1788 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= 66172 MiB
End job on node51 at 2009-07-11 18:32:30