Trace number 2084207

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.147977 0.223647

DiagnosticValue
ASSIGNMENTS100
CHECKS10219
NODES100

General information on the benchmark

Namecsp/rlfapGraphs/
normalized-graph1.xml
MD5SUMa04080f413cb83f1ad6bfb4c8f4b619a
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.147977
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.09	c mistral version 1.545
0.11/0.22	s SATISFIABLE
0.11/0.22	v 30 268 254 16 254 16 142 380 380 142 72 310 526 764 470 708 526 764 16 254 414 652 478 240 100 338 540 778 16 254 792 554 268 30 428 666 722 484 16 254 778 540 526 764 58 296 666 428 30 268 16 254 680 442 30 268 254 16 254 16 484 722 16 254 540 778 352 114 540 778 792 554 380 142 442 680 30 268 722 484 254 16 750 512 30 268 764 526 484 722 680 442 708 470 750 512 380 142 30 268 792 554 652 414 310 72 750 512 254 16 708 470 268 30 652 414 16 254 750 512 142 380 142 380 254 16 30 268 442 680 268 30 722 484 142 380 414 652 254 16 526 764 764 526 526 764 694 456 470 708 736 498 750 512 442 680 736 498 736 498 540 778 268 30 324 86 352 114 254 16 456 694 442 680 254 16 16 254 526 764 100 338 456 694 442 680 456 694 792 554 792 554 380 142 708 470 16 254 512 750
0.11/0.22	d CHECKS 10219
0.11/0.22	d ASSIGNMENTS 100
0.11/0.22	d NODES 100 BACKTRACKS 0 FAILURES 0 RUNTIME 0.09 TOTALTIME 0.12 NODES/s 1111.11 CHECKS/s 113544

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-2084207-1247378894/watcher-2084207-1247378894 -o /tmp/evaluation-result-2084207-1247378894/solver-2084207-1247378894 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2084207-1247378894.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.42 2.26 2.11 4/80 25412
/proc/meminfo: memFree=1677712/2055920 swapFree=4192812/4192956
[pid=25412] ppid=25410 vsize=18576 CPUtime=0
/proc/25412/stat : 25412 (runsolver) R 25410 25412 20092 0 -1 4194368 15 0 0 0 0 0 0 0 19 0 1 0 24955742 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 269028486439 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/25412/statm: 4644 284 249 26 0 2626 0

[startup+0.0124221 s]
/proc/loadavg: 2.42 2.26 2.11 4/80 25412
/proc/meminfo: memFree=1677712/2055920 swapFree=4192812/4192956
[pid=25412] ppid=25410 vsize=2224 CPUtime=0
/proc/25412/stat : 25412 (ld-linux.so.2) D 25410 25412 20092 0 -1 4194304 46 0 2 0 0 0 0 0 18 0 1 0 24955742 2277376 33 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448525156 0 0 4096 0 18446744071563608240 0 0 17 1 0 0
/proc/25412/statm: 556 33 25 29 0 4 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2224

[startup+0.101759 s]
/proc/loadavg: 2.42 2.26 2.11 4/80 25412
/proc/meminfo: memFree=1677712/2055920 swapFree=4192812/4192956
[pid=25412] ppid=25410 vsize=5072 CPUtime=0.02
/proc/25412/stat : 25412 (ld-linux.so.2) R 25410 25412 20092 0 -1 4194304 469 0 11 0 1 1 0 0 18 0 1 0 24955742 5193728 459 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157381179 0 0 4096 0 0 0 0 17 0 0 0
/proc/25412/statm: 1268 459 374 29 0 83 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5072

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

[startup+0.201774 s]
/proc/loadavg: 2.42 2.26 2.11 4/80 25412
/proc/meminfo: memFree=1677712/2055920 swapFree=4192812/4192956
[pid=25412] ppid=25410 vsize=6404 CPUtime=0.11
/proc/25412/stat : 25412 (ld-linux.so.2) R 25410 25412 20092 0 -1 4194304 832 0 11 0 10 1 0 0 18 0 1 0 24955742 6557696 822 996147200 1448431616 1448550632 4294956208 18446744073709551615 134528928 0 0 4096 0 0 0 0 17 0 0 0
/proc/25412/statm: 1601 822 406 29 0 416 0
Current children cumulated CPU time (s) 0.11
Current children cumulated vsize (KiB) 6404

Child status: 0
Real time (s): 0.223647
CPU time (s): 0.147977
CPU user time (s): 0.12898
CPU system time (s): 0.018997
CPU usage (%): 66.1654
Max. virtual memory (cumulated for all children) (KiB): 6404

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.12898
system time used= 0.018997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 875
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= 56
involuntary context switches= 27

runsolver used 0.005999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node26 at 2009-07-12 08:08:14
IDJOB=2084207
IDBENCH=58055
IDSOLVER=769
FILE ID=node26/2084207-1247378894
PBS_JOBID= 9507081
Free space on /tmp= 66396 MiB

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

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

MD5SUM BENCH= a04080f413cb83f1ad6bfb4c8f4b619a
RANDOM SEED=1676448527

node26.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.281
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.281
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:       1678192 kB
Buffers:          4500 kB
Cached:          43304 kB
SwapCached:          0 kB
Active:         310284 kB
Inactive:        16160 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1678192 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1884 kB
Writeback:           0 kB
Mapped:         296508 kB
Slab:            36132 kB
Committed_AS:   917076 kB
PageTables:       2268 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= 66392 MiB
End job on node26 at 2009-07-12 08:08:15