Trace number 201832

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.25681 1.26803

General information on the benchmark

Namerlfap/rlfapScens/
scen3.xml
MD5SUMf0a2bd3f50a529cea49f9ef816c8636b
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 benchmark1.00984
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2760
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2760
Global constraints used (with number of constraints)

Solver Data (download as text)

1.25	
1.25	Time: 1090
1.25	
c 
c 
c 
c solution file
c 
c 

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

converting(/tmp/evaluation/201832-1168149975/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/node12/watcher-201832-1168149975 -o ROOT/results/node12/solver-201832-1168149975 -C 1800 -M 900 /tmp/evaluation/201832-1168149975/Complete/Ordinary/solver /tmp/evaluation/201832-1168149975/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: 2.34 2.09 2.02 5/86 19886
/proc/meminfo: memFree=1256416/2055920 swapFree=4160348/4192956
[pid=19885] ppid=19883 vsize=53472 CPUtime=0
/proc/19885/stat : 19885 (bprolog) R 19883 19885 19752 0 -1 4194304 483 0 0 0 0 0 0 0 18 0 1 0 163392633 54755328 202 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/19885/statm: 13368 203 123 90 0 12906 0

[startup+0.102771 s]
/proc/loadavg: 2.34 2.09 2.02 5/86 19886
/proc/meminfo: memFree=1256416/2055920 swapFree=4160348/4192956
[pid=19885] ppid=19883 vsize=61804 CPUtime=0.09
/proc/19885/stat : 19885 (bprolog) R 19883 19885 19752 0 -1 4194304 1459 0 0 0 9 0 0 0 18 0 1 0 163392633 63287296 1174 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134857292 0 0 4096 2 0 0 0 17 1 0 0
/proc/19885/statm: 15451 1175 157 90 0 14989 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 61804

[startup+0.510843 s]
/proc/loadavg: 2.34 2.09 2.02 5/86 19886
/proc/meminfo: memFree=1256416/2055920 swapFree=4160348/4192956
[pid=19885] ppid=19883 vsize=79860 CPUtime=0.49
/proc/19885/stat : 19885 (bprolog) R 19883 19885 19752 0 -1 4194304 7397 0 0 0 46 3 0 0 21 0 2 0 163392633 81776640 5158 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134661420 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/19885/statm: 19965 5159 177 90 0 19503 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 79860

Child status: 0
Real time (s): 1.26803
CPU time (s): 1.25681
CPU user time (s): 1.10483
CPU system time (s): 0.151976
CPU usage (%): 99.1147
Max. virtual memory (cumulated for all children) (KiB): 157988

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

runsolver used 0.005999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node12 on Sun Jan  7 06:06:15 UTC 2007


IDJOB= 201832
IDBENCH= 3787
FILE ID= node12/201832-1168149975

PBS_JOBID= 3478196

Free space on /tmp= 66315 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScens/scen3.xml
COMMAND LINE= /tmp/evaluation/201832-1168149975/Complete/Ordinary/solver /tmp/evaluation/201832-1168149975/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node12/convwatcher-201832-1168149975 -o ROOT/results/node12/conversion-201832-1168149975 -C 600 -M 900 /tmp/evaluation/201832-1168149975/Complete/Ordinary/conversion /tmp/evaluation/201832-1168149975/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node12/watcher-201832-1168149975 -o ROOT/results/node12/solver-201832-1168149975 -C 1800 -M 900  /tmp/evaluation/201832-1168149975/Complete/Ordinary/solver /tmp/evaluation/201832-1168149975/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  f0a2bd3f50a529cea49f9ef816c8636b

RANDOM SEED= 408477449

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.265
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.265
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:       1257024 kB
Buffers:         55748 kB
Cached:         587836 kB
SwapCached:       4660 kB
Active:         268528 kB
Inactive:       452504 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1257024 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:            1724 kB
Writeback:           0 kB
Mapped:          90568 kB
Slab:            62708 kB
Committed_AS:  4475960 kB
PageTables:       2232 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= 66315 MiB



End job on node12 on Sun Jan  7 06:06:17 UTC 2007