Trace number 195610

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
BPrologCSPSolver70a 2006-12-13SAT 1.08183 1.09663

General information on the benchmark

Namerlfap/rlfapGraphs/
graph2.xml
MD5SUM047e2db4d84b7d874b43ae4e45dd9fec
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.830873
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2245
Maximum constraint arity2
Maximum domain size44
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 (download as text)

1.08	
1.08	Time: 957
1.08	
c 
c 
c 
c solution file
c 
c 

SAT
16 254 114 352 282 44 100 338 72 310 114 352 114 352 58 296 16 254 44 282 282 44 156 394 100 338 72 310 72 310 58 296 352 114 310 72 296 58 254 16 352 114 268 30 86 324 296 58 72 310 114 352 380 142 296 58 296 58 114 352 30 268 30 268 268 30 414 652 16 254 142 380 296 58 338 100 72 310 86 324 86 324 30 268 72 310 72 310 366 128 268 30 310 72 666 428 652 414 338 100 254 16 16 254 16 254 86 324 16 254 268 30 268 30 16 254 128 366 142 380 44 282 44 282 30 268 352 114 142 380 16 254 666 428 380 142 86 324 100 338 30 268 268 30 282 44 380 142 394 156 414 652 16 254 142 380 428 666 44 282 680 442 380 142 16 254 268 30 58 296 156 394 86 324 324 86 114 352 142 380 30 268 324 86 338 100 72 310 142 380 296 58 394 156 58 296 254 16 254 16 352 114 30 268 254 16 72 310 296 58 268 30 142 380 156 394 296 58 310 72 72 310 282 44 128 366 380 142 16 254 44 282 86 324 58 296 72 310 296 58 708 470 72 310 310 72 142 380 268 30 268 30 30 268 142 380 156 394 380 142 254 16 142 380 142 380 338 100 142 380 394 156 58 296 352 114 30 268 310 72 268 30 338 100 142 380 16 254 268 30 380 142 380 142 380 142 142 380 142 380 414 652 254 16 128 366 268 30 380 142 142 380 142 380 310 72 142 380 268 30 394 156 72 310 352 114 310 72 86 324 338 100 652 414 750 512 30 268 380 142 30 268 324 86 30 268 268 30 142 380 142 380 86 324 352 114 254 16 296 58 254 16 44 282 414 652 72 310 338 100 86 324 324 86 254 16 324 86 352 114 268 30 338 100 324 86 268 30 16 254 296 58 16 254 30 268 156 394 30 268 
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/195610-1168113263/unknown)

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/node43/watcher-195610-1168113263 -o ROOT/results/node43/solver-195610-1168113263 -C 1800 -M 900 /tmp/evaluation/195610-1168113263/Complete/Ordinary/solver /tmp/evaluation/195610-1168113263/unknown 1800 

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

/proc/loadavg: 1.39 1.86 1.95 5/82 20531
/proc/meminfo: memFree=1460120/2055920 swapFree=4192812/4192956
[pid=20530] ppid=20528 vsize=18540 CPUtime=0
/proc/20530/stat : 20530 (runsolver) R 20528 20530 20368 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 159725939 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 216849247527 0 0 4096 24578 0 0 0 17 1 0 0
/proc/20530/statm: 4635 279 244 17 0 2626 0

[startup+0.104415 s]
/proc/loadavg: 1.39 1.86 1.95 5/82 20531
/proc/meminfo: memFree=1460120/2055920 swapFree=4192812/4192956
[pid=20530] ppid=20528 vsize=61772 CPUtime=0.08
/proc/20530/stat : 20530 (bprolog) R 20528 20530 20368 0 -1 4194304 1418 0 0 0 8 0 0 0 18 0 1 0 159725939 63254528 1133 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134664585 0 0 4096 2 0 0 0 17 0 0 0
/proc/20530/statm: 15443 1133 173 90 0 14981 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 61772

[startup+0.513492 s]
/proc/loadavg: 1.39 1.86 1.95 5/82 20531
/proc/meminfo: memFree=1460120/2055920 swapFree=4192812/4192956
[pid=20530] ppid=20528 vsize=111080 CPUtime=0.49
/proc/20530/stat : 20530 (bprolog) R 20528 20530 20368 0 -1 4194304 10927 0 0 0 45 4 0 0 23 0 2 0 159725939 113745920 8688 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134865555 0 0 4096 2 18446744073709551615 0 0 17 0 0 0
/proc/20530/statm: 27770 8688 177 90 0 27308 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 111080

Child status: 0
Real time (s): 1.09663
CPU time (s): 1.08183
CPU user time (s): 0.966853
CPU system time (s): 0.114982
CPU usage (%): 98.6508
Max. virtual memory (cumulated for all children) (KiB): 126704

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.966853
system time used= 0.114982
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 25415
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= 59

runsolver used 0.000999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node43 on Sat Jan  6 19:54:24 UTC 2007


IDJOB= 195610
IDBENCH= 3290
FILE ID= node43/195610-1168113263

PBS_JOBID= 3477400

Free space on /tmp= 66482 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphs/graph2.xml
COMMAND LINE= /tmp/evaluation/195610-1168113263/Complete/Ordinary/solver /tmp/evaluation/195610-1168113263/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node43/convwatcher-195610-1168113263 -o ROOT/results/node43/conversion-195610-1168113263 -C 600 -M 900 /tmp/evaluation/195610-1168113263/Complete/Ordinary/conversion /tmp/evaluation/195610-1168113263/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node43/watcher-195610-1168113263 -o ROOT/results/node43/solver-195610-1168113263 -C 1800 -M 900  /tmp/evaluation/195610-1168113263/Complete/Ordinary/solver /tmp/evaluation/195610-1168113263/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  047e2db4d84b7d874b43ae4e45dd9fec

RANDOM SEED= 265635862

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.278
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.278
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:       1460664 kB
Buffers:         37496 kB
Cached:         430208 kB
SwapCached:          0 kB
Active:         173724 kB
Inactive:       353452 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1460664 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3372 kB
Writeback:           0 kB
Mapped:          76240 kB
Slab:            53380 kB
Committed_AS:  3318940 kB
PageTables:       1900 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= 66423 MiB



End job on node43 on Sat Jan  6 19:54:31 UTC 2007