Trace number 277780

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
Toolbar_MaxSat 2007-01-19OPTIMUM 0.903862 1.01768

General information on the benchmark

NameMaxCSP/cnf/2-80-100-1000/
cnf-2-80-500-638341_ext.xml
MD5SUM20adde065cdf89cd6906715e02559f09
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints408
Best CPU time to get the best result obtained on this benchmark4.03039
Satisfiable
(Un)Satisfiability was proved
Number of variables80
Number of constraints458
Maximum constraint arity2
Maximum domain size2
Number of constraints which are defined in extension458
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SOL 0 1 1 1 1 1 0 0 0 1 1 0 1 0 0 0 0 1 1 0 1 1 1 0 1 0 1 1 1 1 1 1 1 0 1 0 0 1 1 0 1 0 0 0 0 0 0 1 0 0 1 1 1 1 1 1 0 1 0 0 1 1 1 0 1 1 1 1 1 1 0 1 1 0 1 1 0 1 1 1 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/277780-1169270606/unknown.xml to /tmp/evaluation/277780-1169270606/unknown.wcsp

Verifier Data (download as text)

50 unsatisfied constraints, 408 satisfied constraints

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node2/watcher-277780-1169270606 -o ROOT/results/node2/solver-277780-1169270606 -C 2400 -M 900 /tmp/evaluation/277780-1169270606/solver.sh /tmp/evaluation/277780-1169270606/unknown 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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.86 1.95 1.94 5/93 19496
/proc/meminfo: memFree=1215584/2055920 swapFree=4180552/4192956
[pid=19495] ppid=19493 vsize=6348 CPUtime=0
/proc/19495/stat : 19495 (solver.sh) R 19493 19495 18727 0 -1 4194304 261 0 0 0 0 0 0 0 22 0 1 0 275456287 6500352 216 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 206378661617 0 0 4096 8192 0 0 0 17 1 0 0
/proc/19495/statm: 1587 216 165 79 0 123 0

[startup+0.105392 s]
/proc/loadavg: 1.86 1.95 1.94 5/93 19496
/proc/meminfo: memFree=1215584/2055920 swapFree=4180552/4192956
[pid=19495] ppid=19493 vsize=47552 CPUtime=0.01
/proc/19495/stat : 19495 (solver.sh) D 19493 19495 18727 0 -1 4194304 745 1704 0 0 0 0 0 1 18 0 1 0 275456287 48693248 358 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 206381481458 0 2147483391 4096 73728 18446744072099781622 0 0 17 1 0 0
/proc/19495/statm: 11888 358 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47552

[startup+0.513465 s]
/proc/loadavg: 1.86 1.95 1.94 5/93 19496
/proc/meminfo: memFree=1215584/2055920 swapFree=4180552/4192956
[pid=19495] ppid=19493 vsize=47552 CPUtime=0.01
/proc/19495/stat : 19495 (solver.sh) S 19493 19495 18727 0 -1 4194304 901 2486 0 0 0 0 0 1 18 0 1 0 275456287 48693248 361 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 206380919642 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/19495/statm: 11888 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47552

Child status: 0
Real time (s): 1.01768
CPU time (s): 0.903862
CPU user time (s): 0.845871
CPU system time (s): 0.057991
CPU usage (%): 88.8164
Max. virtual memory (cumulated for all children) (KiB): 47552

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

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Sat Jan 20 05:23:26 UTC 2007


IDJOB= 277780
IDBENCH= 7655
IDSOLVER= 71
FILE ID= node2/277780-1169270606

PBS_JOBID= 3607305

Free space on /tmp= 66561 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/cnf/2-80-100-1000/cnf-2-80-500-638341_ext.xml
COMMAND LINE= /tmp/evaluation/277780-1169270606/solver.sh /tmp/evaluation/277780-1169270606/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node2/convwatcher-277780-1169270606 -o ROOT/results/node2/conversion-277780-1169270606 -C 600 -M 900 /tmp/evaluation/277780-1169270606/translate /tmp/evaluation/277780-1169270606/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-277780-1169270606 -o ROOT/results/node2/solver-277780-1169270606 -C 2400 -M 900  /tmp/evaluation/277780-1169270606/solver.sh /tmp/evaluation/277780-1169270606/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  20adde065cdf89cd6906715e02559f09

RANDOM SEED= 445196930

TIME LIMIT= 2400 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.259
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.259
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:       1216064 kB
Buffers:         46876 kB
Cached:         641324 kB
SwapCached:        572 kB
Active:         230652 kB
Inactive:       535636 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1216064 kB
SwapTotal:     4192956 kB
SwapFree:      4180552 kB
Dirty:            1776 kB
Writeback:           0 kB
Mapped:          99740 kB
Slab:            58164 kB
Committed_AS:  8137332 kB
PageTables:       2500 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= 66561 MiB



End job on node2 on Sat Jan 20 05:23:28 UTC 2007