Trace number 2084229

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
Mistral 1.545SAT 0.209967 0.261542

DiagnosticValue
ASSIGNMENTS77
CHECKS14843
NODES77

General information on the benchmark

Namecsp/rlfapGraphs/
normalized-graph3.xml
MD5SUM1a813c9bdc27992d76b211942c3214fa
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.209967
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of constraints1134
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1134
Global constraints used (with number of constraints)

Solver Data 

0.00/0.06	c mistral version 1.545
0.14/0.25	s SATISFIABLE
0.14/0.25	v 128 366 666 428 764 526 142 380 666 428 666 428 750 512 114 352 114 352 86 324 792 554 100 338 142 380 708 470 694 456 142 380 764 526 666 428 736 498 16 254 16 254 86 324 58 296 86 324 778 540 128 366 680 442 30 268 72 310 694 456 722 484 16 254 764 526 86 324 30 268 142 380 680 442 58 296 778 540 30 268 764 526 30 268 16 254 792 554 58 296 16 254 72 310 142 380 30 268 44 282 792 554 142 380 86 324 694 456 666 428 792 554 16 254 750 512 156 394 778 540 694 456 16 254 142 380 736 498 680 442 666 428 72 310 128 366 694 456 722 484 708 470 750 512 778 540 72 310 128 366 764 526 58 296 722 484 16 254 792 554 72 310 100 338 86 324 792 554 680 442 128 366 764 526 708 470 30 268 58 296 694 456 722 484 652 414 58 296 778 540 792 554 72 310 30 268 680 442 58 296
0.14/0.25	d CHECKS 14843
0.14/0.25	d ASSIGNMENTS 77
0.14/0.25	d NODES 77 BACKTRACKS 1 FAILURES 1 RUNTIME 0.15 TOTALTIME 0.19 NODES/s 513.333 CHECKS/s 98953.3

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-2084229-1247378900/watcher-2084229-1247378900 -o /tmp/evaluation-result-2084229-1247378900/solver-2084229-1247378900 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2084229-1247378900.xml 

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.48 2.31 2.20 3/82 26572
/proc/meminfo: memFree=1636296/2055920 swapFree=4192812/4192956
[pid=26572] ppid=26570 vsize=2224 CPUtime=0
/proc/26572/stat : 26572 (ld-linux.so.2) D 26570 26572 8169 0 -1 4194304 43 0 0 0 0 0 0 0 18 0 1 0 24957577 2277376 29 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448531911 0 0 4096 0 18446744071563479169 0 0 17 0 0 0
/proc/26572/statm: 556 29 23 29 0 3 0

[startup+0.0723919 s]
/proc/loadavg: 2.48 2.31 2.20 3/82 26572
/proc/meminfo: memFree=1636296/2055920 swapFree=4192812/4192956
[pid=26572] ppid=26570 vsize=5072 CPUtime=0.02
/proc/26572/stat : 26572 (ld-linux.so.2) R 26570 26572 8169 0 -1 4194304 463 0 11 0 1 1 0 0 18 0 1 0 24957577 5193728 453 996147200 1448431616 1448550632 4294956208 18446744073709551615 4160171864 0 0 4096 0 0 0 0 17 1 0 0
/proc/26572/statm: 1268 453 374 29 0 83 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5072

[startup+0.102394 s]
/proc/loadavg: 2.48 2.31 2.20 3/82 26572
/proc/meminfo: memFree=1636296/2055920 swapFree=4192812/4192956
[pid=26572] ppid=26570 vsize=5328 CPUtime=0.05
/proc/26572/stat : 26572 (ld-linux.so.2) R 26570 26572 8169 0 -1 4194304 531 0 11 0 4 1 0 0 18 0 1 0 24957577 5455872 521 996147200 1448431616 1448550632 4294956208 18446744073709551615 134688940 0 0 4096 0 0 0 0 17 1 0 0
/proc/26572/statm: 1332 521 374 29 0 147 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5328

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

[startup+0.201414 s]
/proc/loadavg: 2.48 2.31 2.20 3/82 26572
/proc/meminfo: memFree=1636296/2055920 swapFree=4192812/4192956
[pid=26572] ppid=26570 vsize=6384 CPUtime=0.14
/proc/26572/stat : 26572 (ld-linux.so.2) R 26570 26572 8169 0 -1 4194304 842 0 11 0 13 1 0 0 18 0 1 0 24957577 6537216 832 996147200 1448431616 1448550632 4294956208 18446744073709551615 134860727 0 0 4096 0 0 0 0 17 1 0 0
/proc/26572/statm: 1596 832 406 29 0 411 0
Current children cumulated CPU time (s) 0.14
Current children cumulated vsize (KiB) 6384

Child status: 0
Real time (s): 0.261542
CPU time (s): 0.209967
CPU user time (s): 0.19497
CPU system time (s): 0.014997
CPU usage (%): 80.2804
Max. virtual memory (cumulated for all children) (KiB): 6384

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.19497
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 888
page faults= 12
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 54
involuntary context switches= 24

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node3 at 2009-07-12 08:08:20
IDJOB=2084229
IDBENCH=58057
IDSOLVER=769
FILE ID=node3/2084229-1247378900
PBS_JOBID= 9507109
Free space on /tmp= 66400 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/rlfapGraphs/normalized-graph3.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2084229-1247378900/watcher-2084229-1247378900 -o /tmp/evaluation-result-2084229-1247378900/solver-2084229-1247378900 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2084229-1247378900.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 1a813c9bdc27992d76b211942c3214fa
RANDOM SEED=376726463

node3.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.259
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.259
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:       1636776 kB
Buffers:          7928 kB
Cached:          67620 kB
SwapCached:          0 kB
Active:         179120 kB
Inactive:       183168 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1636776 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1444 kB
Writeback:           0 kB
Mapped:         147324 kB
Slab:            41924 kB
Committed_AS:   372312 kB
PageTables:       2024 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= 66400 MiB
End job on node3 at 2009-07-12 08:08:20