Trace number 2076684

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
bpsolver 09SAT 0.383941 0.391263

General information on the benchmark

Namecsp/rlfapGraphsMod/
normalized-graph2-f24.xml
MD5SUM032be87cbaaa5176d6390981d0a0c94f
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.173973
Satisfiable
(Un)Satisfiability was proved
Number of variables400
Number of constraints2245
Maximum constraint arity2
Maximum domain size22
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2245
Global constraints used (with number of constraints)

Solver Data 

0.19/0.26	c bpsolver version 6.29.2009
0.19/0.26	c converting(HOME/instance-2076684-1247363008)
0.28/0.33	c Converted in 140 ms
0.28/0.37	c solving(HOME/instance-2076684-1247363008,1800000)
0.28/0.37	c solving(HOME/instance-2076684-1247363008,1800000)
0.28/0.38	c (ffc_inout)
0.28/0.38	s SATISFIABLE
0.28/0.38	v 254 16 100 338 44 282 58 296 254 16 366 128 338 100 296 58 128 366 30 268 338 100 128 366 268 30 44 282 254 16 324 86 394 156 338 100 128 366 254 16 72 310 352 114 72 310 324 86 310 72 128 366 380 142 296 58 58 296 44 282 72 310 30 268 30 268 282 44 16 254 142 380 352 114 310 72 282 44 268 30 254 16 310 72 30 268 100 338 394 156 30 268 30 268 100 338 156 394 310 72 324 86 156 394 254 16 30 268 72 310 30 268 282 44 16 254 282 44 142 380 72 310 268 30 114 352 268 30 142 380 16 254 100 338 380 142 366 128 380 142 30 268 296 58 268 30 30 268 394 156 324 86 72 310 142 380 254 16 296 58 296 58 380 142 324 86 58 296 310 72 114 352 296 58 310 72 296 58 142 380 114 352 58 296 268 30 100 338 142 380 324 86 44 282 296 58 254 16 254 16 394 156 86 324 16 254 282 44 338 100 296 58 142 380 156 394 58 296 282 44 282 44 58 296 254 16 380 142 254 16 338 100 100 338 114 352 310 72 86 324 58 296 100 338 72 310 142 380 268 30 324 86 268 30 142 380 100 338 380 142 324 86 142 380 142 380 30 268 44 282 296 58 114 352 30 268 282 44 338 100 86 324 44 282 142 380 268 30 100 338 380 142 380 142 338 100 142 380 142 380 352 114 16 254 58 296 142 380 380 142 142 380 142 380 30 268 142 380 58 296 128 366 366 128 16 254 72 310 268 30 352 114 114 352 282 44 114 352 380 142 352 114 254 16 58 296 30 268 142 380 142 380 254 16 128 366 16 254 338 100 254 16 338 100 72 310 254 16 366 128 16 254 100 338 254 16 86 324 282 44 268 30 254 16 268 30 268 30 254 16 16 254 254 16 268 30 72 310 128 366 
0.28/0.39	
0.28/0.39	c Time=56 ms Backtracks=25
0.28/0.39

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-2076684-1247363008/watcher-2076684-1247363008 -o /tmp/evaluation-result-2076684-1247363008/solver-2076684-1247363008 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2076684-1247363008 1800 

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: 1.65 2.01 1.99 4/82 19101
/proc/meminfo: memFree=1876104/2055920 swapFree=4192812/4192956
[pid=19101] ppid=19099 vsize=18576 CPUtime=0
/proc/19101/stat : 19101 (runsolver) R 19099 19101 15910 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 22992462 19021824 284 996147200 4194304 4302564 548682068528 18446744073709551615 209135922471 0 0 4096 24578 0 0 0 17 1 0 0
/proc/19101/statm: 4644 284 249 26 0 2626 0

[startup+0.20983 s]
/proc/loadavg: 1.65 2.01 1.99 4/82 19101
/proc/meminfo: memFree=1876104/2055920 swapFree=4192812/4192956
[pid=19101] ppid=19099 vsize=62208 CPUtime=0.19
/proc/19101/stat : 19101 (bprolog) R 19099 19101 15910 0 -1 4194304 1148 0 0 0 10 9 0 0 19 0 1 0 22992462 63700992 861 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/19101/statm: 15552 861 176 144 0 15036 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 62208

[startup+0.301834 s]
/proc/loadavg: 1.65 2.01 1.99 4/82 19101
/proc/meminfo: memFree=1876104/2055920 swapFree=4192812/4192956
[pid=19101] ppid=19099 vsize=62208 CPUtime=0.28
/proc/19101/stat : 19101 (bprolog) R 19099 19101 15910 0 -1 4194304 1150 0 0 0 14 14 0 0 20 0 1 0 22992462 63700992 863 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/19101/statm: 15552 863 176 144 0 15036 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 62208

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

Child status: 0
Real time (s): 0.391263
CPU time (s): 0.383941
CPU user time (s): 0.213967
CPU system time (s): 0.169974
CPU usage (%): 98.1286
Max. virtual memory (cumulated for all children) (KiB): 62208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.213967
system time used= 0.169974
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1846
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 6
involuntary context switches= 3

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node41 at 2009-07-12 03:43:28
IDJOB=2076684
IDBENCH=56483
IDSOLVER=770
FILE ID=node41/2076684-1247363008
PBS_JOBID= 9506891
Free space on /tmp= 65876 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/rlfapGraphsMod/normalized-graph2-f24.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2076684-1247363008/watcher-2076684-1247363008 -o /tmp/evaluation-result-2076684-1247363008/solver-2076684-1247363008 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2076684-1247363008 1800

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

MD5SUM BENCH= 032be87cbaaa5176d6390981d0a0c94f
RANDOM SEED=1013350139

node41.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.212
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	: 5931.00
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.212
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:       1876584 kB
Buffers:         13576 kB
Cached:          85704 kB
SwapCached:          0 kB
Active:         111724 kB
Inactive:        22212 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1876584 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3464 kB
Writeback:           0 kB
Mapped:          55104 kB
Slab:            30576 kB
Committed_AS:   215812 kB
PageTables:       1812 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= 65876 MiB
End job on node41 at 2009-07-12 03:43:28