Trace number 2061246

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.59091 0.521028

DiagnosticValue
CHECKS0
NODES3

General information on the benchmark

Namecsp/QG5/
normalized-quasigroup5-5.xml
MD5SUMc75f5ab93ac6ff5a61cd3a1735512fe8
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.010998
Satisfiable
(Un)Satisfiability was proved
Number of variables65
Number of constraints50
Maximum constraint arity7
Maximum domain size5
Number of constraints which are defined in extension0
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)alldifferent(10),element(40)

Solver Data 

0.45/0.48	s SATISFIABLE
0.45/0.48	v 1 3 4 5 2 4 2 5 3 1 5 1 3 2 4 2 5 1 4 3 3 4 2 1 5 5 2 2 3 3 4 4 5 5 1 4 3 1 4 3 5 2 1 4 2 5 4 1 5 3 1 1 2 5 3 2 5 4 1 3 2 1 3 2 4 
0.45/0.48	d AC 32
0.45/0.48	d RUNTIME 0.394
0.45/0.48	d NODES 3
0.45/0.48	d NODES/s 8
0.45/0.48	d BACKTRACKS 0
0.45/0.48	d BACKTRACKS/s 0
0.45/0.48	d CHECKS 0
0.45/0.48	d CHECKS/s 0
0.45/0.48	c SAT 0.394 TIME      3 NDS    102 PARSTIME      175 BUILDPB       117 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-2061246-1247326850/watcher-2061246-1247326850 -o /tmp/evaluation-result-2061246-1247326850/solver-2061246-1247326850 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2061246-1247326850.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: 0.79 0.95 1.12 3/83 14016
/proc/meminfo: memFree=903536/2055920 swapFree=4192956/4192956
[pid=14016] ppid=14014 vsize=144 CPUtime=0
/proc/14016/stat : 14016 (java) R 14014 14016 13111 0 -1 0 209 0 0 0 0 0 0 0 20 0 1 0 19750268 147456 14 996147200 134512640 134550932 4294955840 18446744073709551615 6319548 0 0 4096 0 0 0 0 17 1 0 0
/proc/14016/statm: 37 20 14 9 0 3 0

[startup+0.0725679 s]
/proc/loadavg: 0.79 0.95 1.12 3/83 14016
/proc/meminfo: memFree=903536/2055920 swapFree=4192956/4192956
[pid=14016] ppid=14014 vsize=862292 CPUtime=0.07
/proc/14016/stat : 14016 (java) S 14014 14016 13111 0 -1 0 3252 0 1 0 6 1 0 0 18 0 9 0 19750268 882987008 2720 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/14016/statm: 215573 2721 1296 9 0 210442 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 862292

[startup+0.102186 s]
/proc/loadavg: 0.79 0.95 1.12 3/83 14016
/proc/meminfo: memFree=903536/2055920 swapFree=4192956/4192956
[pid=14016] ppid=14014 vsize=865124 CPUtime=0.09
/proc/14016/stat : 14016 (java) S 14014 14016 13111 0 -1 0 3995 0 1 0 8 1 0 0 18 0 9 0 19750268 885886976 3442 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/14016/statm: 216281 3443 1775 9 0 210749 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 865124

[startup+0.301264 s]
/proc/loadavg: 0.79 0.95 1.12 3/83 14016
/proc/meminfo: memFree=903536/2055920 swapFree=4192956/4192956
[pid=14016] ppid=14014 vsize=865264 CPUtime=0.34
/proc/14016/stat : 14016 (java) S 14014 14016 13111 0 -1 0 5546 0 1 0 31 3 0 0 18 0 9 0 19750268 886030336 4940 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/14016/statm: 216316 4941 1941 9 0 210784 0
Current children cumulated CPU time (s) 0.34
Current children cumulated vsize (KiB) 865264

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

[startup+0.501264 s]
/proc/loadavg: 0.79 0.95 1.12 3/83 14016
/proc/meminfo: memFree=903536/2055920 swapFree=4192956/4192956
[pid=14016] ppid=14014 vsize=865588 CPUtime=0.58
/proc/14016/stat : 14016 (java) S 14014 14016 13111 0 -1 0 6587 0 1 0 54 4 0 0 18 0 9 0 19750268 886362112 5966 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/14016/statm: 216397 5966 1963 9 0 210865 0
Current children cumulated CPU time (s) 0.58
Current children cumulated vsize (KiB) 865588

Child status: 0
Real time (s): 0.521028
CPU time (s): 0.59091
CPU user time (s): 0.544917
CPU system time (s): 0.045993
CPU usage (%): 113.412
Max. virtual memory (cumulated for all children) (KiB): 865588

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.544917
system time used= 0.045993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6591
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= 171
involuntary context switches= 31

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node86 at 2009-07-11 17:40:50
IDJOB=2061246
IDBENCH=53791
IDSOLVER=737
FILE ID=node86/2061246-1247326850
PBS_JOBID= 9506463
Free space on /tmp= 66304 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/QG5/normalized-quasigroup5-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-2061246-1247326850/watcher-2061246-1247326850 -o /tmp/evaluation-result-2061246-1247326850/solver-2061246-1247326850 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2061246-1247326850.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= c75f5ab93ac6ff5a61cd3a1735512fe8
RANDOM SEED=860635488

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        903952 kB
Buffers:         64928 kB
Cached:         979280 kB
SwapCached:          0 kB
Active:         358720 kB
Inactive:       717704 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        903952 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            2868 kB
Writeback:           0 kB
Mapped:          50416 kB
Slab:            60604 kB
Committed_AS:   177472 kB
PageTables:       1972 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= 66304 MiB
End job on node86 at 2009-07-11 17:40:50