Trace number 2074072

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.994848 0.833236

DiagnosticValue
CHECKS0
NODES25

General information on the benchmark

Namecsp/os-taillard-5/
normalized-os-taillard-5-100-1.xml
MD5SUM49e45c241d4fb651761c885f5c09f8f5
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.023995
Satisfiable
(Un)Satisfiability was proved
Number of variables25
Number of constraints100
Maximum constraint arity2
Maximum domain size262
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
Global constraints used (with number of constraints)

Solver Data

0.97/0.81	s SATISFIABLE
0.97/0.81	v 0 120 83 159 240 15 201 194 40 104 37 0 240 175 256 40 104 175 83 0 104 159 201 15 0 
0.97/0.81	d AC 32
0.97/0.81	d RUNTIME 0.719
0.97/0.81	d NODES 25
0.97/0.81	d NODES/s 35
0.97/0.81	d BACKTRACKS 1
0.97/0.81	d BACKTRACKS/s 1
0.97/0.81	d CHECKS 0
0.97/0.81	d CHECKS/s 0
0.97/0.81	c SAT 0.719 TIME      25 NDS    184 PARSTIME      285 BUILDPB       250 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-2074072-1247359089/watcher-2074072-1247359089 -o /tmp/evaluation-result-2074072-1247359089/solver-2074072-1247359089 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2074072-1247359089.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.55 1.50 1.81 2/68 19067
/proc/meminfo: memFree=1883888/2055920 swapFree=4192812/4192956
[pid=19067] ppid=19065 vsize=1616 CPUtime=0
/proc/19067/stat : 19067 (java) D 19065 19067 17060 0 -1 0 194 0 0 0 0 0 0 0 18 0 1 0 22973546 1654784 161 996147200 134512640 134550932 4294956000 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099937270 0 0 17 1 0 0
/proc/19067/statm: 404 161 124 9 0 46 0

[startup+0.0878869 s]
/proc/loadavg: 0.55 1.50 1.81 2/68 19067
/proc/meminfo: memFree=1883888/2055920 swapFree=4192812/4192956
[pid=19067] ppid=19065 vsize=865020 CPUtime=0.08
/proc/19067/stat : 19067 (java) S 19065 19067 17060 0 -1 0 3824 0 1 0 7 1 0 0 18 0 9 0 22973546 885780480 3279 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/19067/statm: 216255 3279 1726 9 0 210723 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 865020

[startup+0.101888 s]
/proc/loadavg: 0.55 1.50 1.81 2/68 19067
/proc/meminfo: memFree=1883888/2055920 swapFree=4192812/4192956
[pid=19067] ppid=19065 vsize=865020 CPUtime=0.09
/proc/19067/stat : 19067 (java) S 19065 19067 17060 0 -1 0 3978 0 1 0 8 1 0 0 18 0 9 0 22973546 885780480 3425 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/19067/statm: 216255 3425 1775 9 0 210723 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 865020

[startup+0.301913 s]
/proc/loadavg: 0.55 1.50 1.81 2/68 19067
/proc/meminfo: memFree=1883888/2055920 swapFree=4192812/4192956
[pid=19067] ppid=19065 vsize=865168 CPUtime=0.34
/proc/19067/stat : 19067 (java) S 19065 19067 17060 0 -1 0 5433 0 1 0 32 2 0 0 18 0 9 0 22973546 885932032 4837 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/19067/statm: 216292 4837 1919 9 0 210760 0
Current children cumulated CPU time (s) 0.34
Current children cumulated vsize (KiB) 865168

[startup+0.701954 s]
/proc/loadavg: 0.55 1.50 1.81 2/68 19067
/proc/meminfo: memFree=1883888/2055920 swapFree=4192812/4192956
[pid=19067] ppid=19065 vsize=865300 CPUtime=0.84
/proc/19067/stat : 19067 (java) S 19065 19067 17060 0 -1 0 7643 0 1 0 81 3 0 0 18 0 9 0 22973546 886067200 7022 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/19067/statm: 216325 7022 1978 9 0 210793 0
Current children cumulated CPU time (s) 0.84
Current children cumulated vsize (KiB) 865300

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

[startup+0.801967 s]
/proc/loadavg: 0.55 1.50 1.81 2/68 19067
/proc/meminfo: memFree=1883888/2055920 swapFree=4192812/4192956
[pid=19067] ppid=19065 vsize=865300 CPUtime=0.97
/proc/19067/stat : 19067 (java) S 19065 19067 17060 0 -1 0 7996 0 1 0 93 4 0 0 18 0 9 0 22973546 886067200 7375 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/19067/statm: 216325 7375 1978 9 0 210793 0
Current children cumulated CPU time (s) 0.97
Current children cumulated vsize (KiB) 865300

Child status: 0
Real time (s): 0.833236
CPU time (s): 0.994848
CPU user time (s): 0.948855
CPU system time (s): 0.045993
CPU usage (%): 119.396
Max. virtual memory (cumulated for all children) (KiB): 865300

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.948855
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= 8072
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= 277
involuntary context switches= 38

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data

Begin job on node91 at 2009-07-12 02:38:09
IDJOB=2074072
IDBENCH=56049
IDSOLVER=737
FILE ID=node91/2074072-1247359089
PBS_JOBID= 9506970
Free space on /tmp= 66116 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/os-taillard-5/normalized-os-taillard-5-100-1.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-2074072-1247359089/watcher-2074072-1247359089 -o /tmp/evaluation-result-2074072-1247359089/solver-2074072-1247359089 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2074072-1247359089.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= 49e45c241d4fb651761c885f5c09f8f5
RANDOM SEED=2042374344

node91.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.241
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.241
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:       1884304 kB
Buffers:         17364 kB
Cached:          85316 kB
SwapCached:          0 kB
Active:          94340 kB
Inactive:        24540 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1884304 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2768 kB
Writeback:           0 kB
Mapped:          25944 kB
Slab:            38300 kB
Committed_AS:   128536 kB
PageTables:       1556 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= 66112 MiB
End job on node91 at 2009-07-12 02:38:10