Trace number 2072378

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.552915 0.579242

DiagnosticValue
CHECKS0
NODES1005

General information on the benchmark

Namecsp/pseudoGLB/
normalized-reduced-prob3.xml
MD5SUMe9fd797fc7f94dfb67a5763e936a65c7
Bench CategoryAlldiff+Elt+WSum (alldiff,element,weightedsum)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.007998
Satisfiable
(Un)Satisfiability was proved
Number of variables52
Number of constraints2
Maximum constraint arity52
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)weightedsum(2)

Solver Data

0.48/0.56	s SATISFIABLE
0.48/0.56	v 1 1 1 1 0 1 1 0 0 0 1 1 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0.48/0.56	d AC 32
0.48/0.56	d RUNTIME 0.454
0.48/0.56	d NODES 1005
0.48/0.56	d NODES/s 2214
0.48/0.56	d BACKTRACKS 1053
0.48/0.56	d BACKTRACKS/s 2319
0.48/0.56	d CHECKS 0
0.48/0.56	d CHECKS/s 0
0.48/0.56	c SAT 0.454 TIME      1005 NDS    92 PARSTIME      213 BUILDPB       149 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-2072378-1247356405/watcher-2072378-1247356405 -o /tmp/evaluation-result-2072378-1247356405/solver-2072378-1247356405 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2072378-1247356405.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: 1.92 1.99 1.99 3/81 16676
/proc/meminfo: memFree=1843888/2055920 swapFree=4192812/4192956
[pid=16676] ppid=16674 vsize=1612 CPUtime=0
/proc/16676/stat : 16676 (java) R 16674 16676 16020 0 -1 0 149 0 0 0 0 0 0 0 21 0 1 0 22707754 1650688 121 996147200 134512640 134550932 4294956016 18446744073709551615 4160589351 0 0 4096 0 0 0 0 17 0 0 0
/proc/16676/statm: 403 121 86 9 0 45 0

[startup+0.059452 s]
/proc/loadavg: 1.92 1.99 1.99 3/81 16676
/proc/meminfo: memFree=1843888/2055920 swapFree=4192812/4192956
[pid=16676] ppid=16674 vsize=862208 CPUtime=0.05
/proc/16676/stat : 16676 (java) S 16674 16676 16020 0 -1 0 2821 0 1 0 3 2 0 0 18 0 9 0 22707754 882900992 2346 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16676/statm: 215552 2346 1134 9 0 210421 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 862208

[startup+0.102456 s]
/proc/loadavg: 1.92 1.99 1.99 3/81 16676
/proc/meminfo: memFree=1843888/2055920 swapFree=4192812/4192956
[pid=16676] ppid=16674 vsize=864064 CPUtime=0.09
/proc/16676/stat : 16676 (java) S 16674 16676 16020 0 -1 0 3883 0 1 0 7 2 0 0 18 0 9 0 22707754 884801536 3330 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16676/statm: 216016 3330 1747 9 0 210484 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 864064

[startup+0.302475 s]
/proc/loadavg: 1.92 1.99 1.99 3/81 16676
/proc/meminfo: memFree=1843888/2055920 swapFree=4192812/4192956
[pid=16676] ppid=16674 vsize=864532 CPUtime=0.28
/proc/16676/stat : 16676 (java) S 16674 16676 16020 0 -1 0 5283 0 1 0 25 3 0 0 18 0 9 0 22707754 885280768 4683 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16676/statm: 216133 4683 1924 9 0 210601 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 864532

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

[startup+0.50249 s]
/proc/loadavg: 1.92 1.99 1.99 3/81 16676
/proc/meminfo: memFree=1843888/2055920 swapFree=4192812/4192956
[pid=16676] ppid=16674 vsize=864532 CPUtime=0.48
/proc/16676/stat : 16676 (java) S 16674 16676 16020 0 -1 0 6295 0 1 0 43 5 0 0 18 0 9 0 22707754 885280768 5681 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16676/statm: 216133 5681 1953 9 0 210601 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 864532

Child status: 0
Real time (s): 0.579242
CPU time (s): 0.552915
CPU user time (s): 0.492925
CPU system time (s): 0.05999
CPU usage (%): 95.4549
Max. virtual memory (cumulated for all children) (KiB): 864532

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.492925
system time used= 0.05999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6467
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= 533
involuntary context switches= 506

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data

Begin job on node8 at 2009-07-12 01:53:25
IDJOB=2072378
IDBENCH=55680
IDSOLVER=737
FILE ID=node8/2072378-1247356405
PBS_JOBID= 9506927
Free space on /tmp= 66268 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/pseudoGLB/normalized-reduced-prob3.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-2072378-1247356405/watcher-2072378-1247356405 -o /tmp/evaluation-result-2072378-1247356405/solver-2072378-1247356405 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2072378-1247356405.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= e9fd797fc7f94dfb67a5763e936a65c7
RANDOM SEED=577694820

node8.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.213
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.213
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:       1844368 kB
Buffers:         10368 kB
Cached:          65180 kB
SwapCached:          0 kB
Active:         136676 kB
Inactive:        28356 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1844368 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2692 kB
Writeback:           0 kB
Mapped:         107196 kB
Slab:            31516 kB
Committed_AS:   895184 kB
PageTables:       1904 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= 66268 MiB
End job on node8 at 2009-07-12 01:53:26