Trace number 268008

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, and are wall clock time (not CPU 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
VALCSP 3.1SAT 0.199968 0.210356

DiagnosticValue
CHECKS895896
NODES200

General information on the benchmark

Namerlfap/rlfapGraphs/
graph1.xml
MD5SUM7d2754cc44d2423629dbe49c143cee41
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.405937
SatisfiableYES
(Un)Satisfiability was provedYES
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 (download as text)

0.20	s SATISFIABLE
0.20	v 324 86 254 16 414 652 380 142 380 142 282 44 324 86 296 58 442 680 254 16 296 58 240 478 296 58 428 666 16 254 282 44 30 268 44 282 100 338 16 254 30 268 44 282 254 16 128 366 72 310 58 296 282 44 268 30 16 254 254 16 366 128 30 268 100 338 30 268 282 44 30 268 380 142 86 324 156 394 30 268 58 296 142 380 58 296 324 86 156 394 338 100 16 254 58 296 142 380 296 58 414 652 16 254 366 128 128 366 16 254 58 296 268 30 114 352 72 310 16 254 142 380 142 380 254 16 352 114 268 30 72 310 44 282 142 380 44 282 16 254 296 58 142 380 100 338 414 652 456 694 338 100 72 310 128 366 338 100 310 72 366 128 414 652 442 680 428 666 254 16 100 338 296 58 254 16 30 268 268 30 652 414 58 296 324 86 100 338 86 324 156 394 380 142 366 128 16 254 114 352 
0.20	d CHECKS 895896
0.20	d NODES 200

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node76/watcher-268008-1168977863 -o ROOT/results/node76/solver-268008-1168977863 -C 1800 -M 900 /tmp/evaluation/268008-1168977863/VALCSP /tmp/evaluation/268008-1168977863/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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.102898 s]
/proc/loadavg: 0.00 0.00 0.00 4/75 17803
/proc/meminfo: memFree=1337184/2055888 swapFree=4095388/4096564
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 0.00 0.00 0.00 4/75 17803
/proc/meminfo: memFree=1337184/2055888 swapFree=4095388/4096564
[pid=17802] ppid=17799 vsize=0 CPUtime=0.19
/proc/17802/stat : 17802 (VALCSP) R 17799 17802 17444 0 -1 4194308 1954 0 0 0 19 0 0 0 21 0 1 0 246184027 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 0 0 0 17 1 0 0
/proc/17802/statm: 0 0 0 0 0 0 0

Child status: 0
Real time (s): 0.210356
CPU time (s): 0.199968
CPU user time (s): 0.19097
CPU system time (s): 0.008998
CPU usage (%): 95.0617
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Tue Jan 16 20:04:29 UTC 2007


IDJOB= 268008
IDBENCH= 3293
IDSOLVER= 90
FILE ID= node76/268008-1168977863

PBS_JOBID= 3566114

Free space on /tmp= 66651 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphs/graph1.xml
COMMAND LINE= /tmp/evaluation/268008-1168977863/VALCSP /tmp/evaluation/268008-1168977863/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-268008-1168977863 -o ROOT/results/node76/solver-268008-1168977863 -C 1800 -M 900  /tmp/evaluation/268008-1168977863/VALCSP /tmp/evaluation/268008-1168977863/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  7d2754cc44d2423629dbe49c143cee41

RANDOM SEED= 101355900

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1338136 kB
Buffers:         52540 kB
Cached:         570880 kB
SwapCached:        276 kB
Active:          78408 kB
Inactive:       564948 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1338136 kB
SwapTotal:     4096564 kB
SwapFree:      4095388 kB
Dirty:             692 kB
Writeback:           0 kB
Mapped:          29140 kB
Slab:            60476 kB
Committed_AS:  7596124 kB
PageTables:       1624 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66651 MiB



End job on node76 on Tue Jan 16 20:04:35 UTC 2007