Trace number 268929

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.637902 0.645978

DiagnosticValue
CHECKS14113800
NODES2521

General information on the benchmark

Nametightness/tightness0.5/
rand-2-40-25-180-500-49_ext.xml
MD5SUM452db4ac7b92085726272d485646a151
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.6509
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints180
Maximum constraint arity2
Maximum domain size25
Number of constraints which are defined in extension180
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.64	s SATISFIABLE
0.64	v 18 5 22 11 10 11 0 18 3 10 3 24 7 15 18 6 3 1 3 24 18 1 23 15 11 22 9 15 0 13 14 3 11 4 23 5 15 21 22 23 
0.64	d CHECKS 1.41138e+07
0.64	d NODES 2521

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/node29/watcher-268929-1168980031 -o ROOT/results/node29/solver-268929-1168980031 -C 1800 -M 900 /tmp/evaluation/268929-1168980031/VALCSP /tmp/evaluation/268929-1168980031/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

/proc/loadavg: 0.13 0.56 0.69 5/86 3142
/proc/meminfo: memFree=1502648/2055920 swapFree=4161368/4192956
[pid=3141] ppid=3136 vsize=18540 CPUtime=0
/proc/3141/stat : 3141 (runsolver) R 3136 3141 2951 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 246398273 18984960 279 18446744073709551615 4194304 4267372 548682069088 18446744073709551615 221780700455 0 0 4096 24578 0 0 0 17 1 0 0
/proc/3141/statm: 4635 279 244 17 0 2626 0

[startup+0.103152 s]
/proc/loadavg: 0.13 0.56 0.69 5/86 3142
/proc/meminfo: memFree=1502648/2055920 swapFree=4161368/4192956
[pid=3141] ppid=3136 vsize=2260 CPUtime=0.09
/proc/3141/stat : 3141 (VALCSP) R 3136 3141 2951 0 -1 4194304 304 0 0 0 9 0 0 0 18 0 1 0 246398273 2314240 282 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 4588641 0 0 4096 0 0 0 0 17 0 0 0
/proc/3141/statm: 565 282 64 8 0 237 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2260

[startup+0.511175 s]
/proc/loadavg: 0.13 0.56 0.69 5/86 3142
/proc/meminfo: memFree=1502648/2055920 swapFree=4161368/4192956
[pid=3141] ppid=3136 vsize=3712 CPUtime=0.5
/proc/3141/stat : 3141 (VALCSP) R 3136 3141 2951 0 -1 4194304 684 0 0 0 50 0 0 0 22 0 1 0 246398273 3801088 662 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134524827 0 0 4096 0 0 0 0 17 0 0 0
/proc/3141/statm: 928 662 66 8 0 600 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 3712

Child status: 0
Real time (s): 0.645978
CPU time (s): 0.637902
CPU user time (s): 0.632903
CPU system time (s): 0.004999
CPU usage (%): 98.7498
Max. virtual memory (cumulated for all children) (KiB): 3712

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

runsolver used 0.000999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node29 on Tue Jan 16 20:40:38 UTC 2007


IDJOB= 268929
IDBENCH= 5632
IDSOLVER= 90
FILE ID= node29/268929-1168980031

PBS_JOBID= 3566276

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.5/rand-2-40-25-180-500-49_ext.xml
COMMAND LINE= /tmp/evaluation/268929-1168980031/VALCSP /tmp/evaluation/268929-1168980031/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node29/watcher-268929-1168980031 -o ROOT/results/node29/solver-268929-1168980031 -C 1800 -M 900  /tmp/evaluation/268929-1168980031/VALCSP /tmp/evaluation/268929-1168980031/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  452db4ac7b92085726272d485646a151

RANDOM SEED= 26847408

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.241
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.241
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:       1504000 kB
Buffers:         50980 kB
Cached:         390992 kB
SwapCached:       2476 kB
Active:         126088 kB
Inactive:       345632 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1504000 kB
SwapTotal:     4192956 kB
SwapFree:      4161368 kB
Dirty:             504 kB
Writeback:           0 kB
Mapped:          44856 kB
Slab:            65292 kB
Committed_AS:  4857904 kB
PageTables:       2220 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= 66564 MiB



End job on node29 on Tue Jan 16 20:40:48 UTC 2007