Trace number 2085919

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.761884 0.783528

DiagnosticValue
CHECKS0
NODES77

General information on the benchmark

Namecsp/graphColoring/mug/
normalized-mug88-25-4.xml
MD5SUMede507a351e591440e7b9dc9cc3a05e7
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.012997
Satisfiable
(Un)Satisfiability was proved
Number of variables88
Number of constraints146
Maximum constraint arity2
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension146
Global constraints used (with number of constraints)

Solver Data

0.69/0.76	s SATISFIABLE
0.69/0.76	v 2 2 3 0 0 0 3 2 1 3 0 1 2 2 1 2 1 3 2 0 2 2 1 3 0 2 2 0 2 0 2 0 3 1 1 0 0 1 0 3 1 3 2 0 0 3 3 1 2 2 0 0 3 2 0 0 2 1 2 3 1 1 0 2 2 3 1 1 3 2 2 0 3 0 3 0 3 0 1 3 0 1 2 1 3 1 2 3 
0.69/0.76	d AC 32
0.69/0.76	d RUNTIME 0.656
0.69/0.76	d NODES 77
0.69/0.76	d NODES/s 117
0.69/0.76	d BACKTRACKS 0
0.69/0.76	d BACKTRACKS/s 0
0.69/0.76	d CHECKS 0
0.69/0.76	d CHECKS/s 0
0.69/0.76	c SAT 0.656 TIME      77 NDS    291 PARSTIME      264 BUILDPB       101 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-2085919-1247382921/watcher-2085919-1247382921 -o /tmp/evaluation-result-2085919-1247382921/solver-2085919-1247382921 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2085919-1247382921.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.01 2.00 2.00 3/84 26242
/proc/meminfo: memFree=1606608/2055920 swapFree=4192812/4192956
[pid=26242] ppid=26240 vsize=152 CPUtime=0
/proc/26242/stat : 26242 (java) R 26240 26242 25606 0 -1 0 222 0 0 0 0 0 0 0 18 0 1 0 25358773 155648 26 996147200 134512640 134550932 4294955840 18446744073709551615 12591403 0 0 4096 0 0 0 0 17 0 0 0
/proc/26242/statm: 38 26 19 9 0 4 0

[startup+0.0443229 s]
/proc/loadavg: 2.01 2.00 2.00 3/84 26242
/proc/meminfo: memFree=1606608/2055920 swapFree=4192812/4192956
[pid=26242] ppid=26240 vsize=859892 CPUtime=0.03
/proc/26242/stat : 26242 (java) S 26240 26242 25606 0 -1 0 2379 0 1 0 2 1 0 0 18 0 5 0 25358773 880529408 1941 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800971 18446744073709551615 0 0 17 0 0 0
/proc/26242/statm: 214973 1941 905 9 0 209888 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 859892

[startup+0.101326 s]
/proc/loadavg: 2.01 2.00 2.00 3/84 26242
/proc/meminfo: memFree=1606608/2055920 swapFree=4192812/4192956
[pid=26242] ppid=26240 vsize=864096 CPUtime=0.09
/proc/26242/stat : 26242 (java) S 26240 26242 25606 0 -1 0 3868 0 1 0 7 2 0 0 18 0 9 0 25358773 884834304 3318 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26242/statm: 216024 3318 1742 9 0 210492 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 864096

[startup+0.30135 s]
/proc/loadavg: 2.01 2.00 2.00 3/84 26242
/proc/meminfo: memFree=1606608/2055920 swapFree=4192812/4192956
[pid=26242] ppid=26240 vsize=864372 CPUtime=0.29
/proc/26242/stat : 26242 (java) S 26240 26242 25606 0 -1 0 4768 0 1 0 26 3 0 0 18 0 9 0 25358773 885116928 4184 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26242/statm: 216093 4184 1880 9 0 210561 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 864372

[startup+0.701397 s]
/proc/loadavg: 2.01 2.00 2.00 3/84 26242
/proc/meminfo: memFree=1606608/2055920 swapFree=4192812/4192956
[pid=26242] ppid=26240 vsize=864584 CPUtime=0.69
/proc/26242/stat : 26242 (java) S 26240 26242 25606 0 -1 0 6940 0 1 0 64 5 0 0 18 0 9 0 25358773 885334016 6321 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26242/statm: 216146 6321 1960 9 0 210614 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 864584

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

Child status: 0
Real time (s): 0.783528
CPU time (s): 0.761884
CPU user time (s): 0.696894
CPU system time (s): 0.06499
CPU usage (%): 97.2376
Max. virtual memory (cumulated for all children) (KiB): 864584

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.696894
system time used= 0.06499
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7088
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= 644
involuntary context switches= 634

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data

Begin job on node28 at 2009-07-12 09:15:22
IDJOB=2085919
IDBENCH=58530
IDSOLVER=737
FILE ID=node28/2085919-1247382921
PBS_JOBID= 9507279
Free space on /tmp= 66116 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/graphColoring/mug/normalized-mug88-25-4.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-2085919-1247382921/watcher-2085919-1247382921 -o /tmp/evaluation-result-2085919-1247382921/solver-2085919-1247382921 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2085919-1247382921.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= ede507a351e591440e7b9dc9cc3a05e7
RANDOM SEED=698561750

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:       1607088 kB
Buffers:          8672 kB
Cached:          70548 kB
SwapCached:          0 kB
Active:         371460 kB
Inactive:        28196 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1607088 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3052 kB
Writeback:           0 kB
Mapped:         333088 kB
Slab:            33708 kB
Committed_AS:   879620 kB
PageTables:       2400 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 node28 at 2009-07-12 09:15:22