Trace number 2073552

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
pcs-restart 0.3.2SAT 0.797878 0.812065

DiagnosticValue
ASSIGNMENTS0

General information on the benchmark

Namecsp/bddSmall/
normalized-bdd-21-133-18-78-25_ext.xml
MD5SUM3ae432f57037edf38a55627c9dd43e63
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.797878
Satisfiable
(Un)Satisfiability was proved
Number of variables21
Number of constraints133
Maximum constraint arity18
Maximum domain size2
Number of constraints which are defined in extension133
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.00/0.05	c small-domain mode
0.00/0.05	c Seed is 122529042
0.00/0.05	c Constructing HOME/instance-2073552-1247712060.xml  with 133 constraints
0.67/0.79	c Solving 0 backtracks
0.77/0.81	s SATISFIABLE
0.77/0.81	c V0=0, V1=0, V2=0, V3=0, V4=0, V5=0, V6=0, V7=0, V8=0, V9=0, V10=0, V11=0, V12=0, V13=0, V14=0, V15=0, V16=0, V17=0, V18=0, V19=0, V20=0, 
0.77/0.81	v 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0.77/0.81	d ASSIGNMENTS 0

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2073552-1247712060/watcher-2073552-1247712060 -o /tmp/evaluation-result-2073552-1247712060/solver-2073552-1247712060 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 122529042 HOME/instance-2073552-1247712060.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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 s]
/proc/loadavg: 2.00 2.01 2.04 4/81 16572
/proc/meminfo: memFree=1358032/2055920 swapFree=4192812/4192956
[pid=16572] ppid=16570 vsize=18576 CPUtime=0
/proc/16572/stat : 16572 (runsolver) R 16570 16572 16386 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 58270202 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 213116316967 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16572/statm: 4644 284 249 26 0 2626 0

[startup+0.010513 s]
/proc/loadavg: 2.00 2.01 2.04 4/81 16572
/proc/meminfo: memFree=1358032/2055920 swapFree=4192812/4192956
[pid=16572] ppid=16570 vsize=5356 CPUtime=0
/proc/16572/stat : 16572 (pcssolve) S 16570 16572 16386 0 -1 4194304 305 0 0 0 0 0 0 0 20 0 1 0 58270202 5484544 242 996147200 4194304 4889804 548682068800 18446744073709551615 213116314436 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/16572/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.101536 s]
/proc/loadavg: 2.00 2.01 2.04 4/81 16572
/proc/meminfo: memFree=1358032/2055920 swapFree=4192812/4192956
[pid=16572] ppid=16570 vsize=5844 CPUtime=0.07
/proc/16572/stat : 16572 (pcs.small) R 16570 16572 16386 0 -1 4194304 1041 3860 0 0 4 0 1 2 22 0 1 0 58270202 5984256 650 996147200 134512640 135095119 4294956304 18446744073709551615 134653755 0 0 4096 0 0 0 0 17 1 0 0
/proc/16572/statm: 1461 650 361 142 0 415 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5844

[startup+0.301577 s]
/proc/loadavg: 2.00 2.01 2.04 4/81 16572
/proc/meminfo: memFree=1358032/2055920 swapFree=4192812/4192956
[pid=16572] ppid=16570 vsize=9540 CPUtime=0.27
/proc/16572/stat : 16572 (pcs.small) R 16570 16572 16386 0 -1 4194304 2093 3860 0 0 24 0 1 2 23 0 1 0 58270202 9768960 1702 996147200 134512640 135095119 4294956304 18446744073709551615 134681702 0 0 4096 0 0 0 0 17 1 0 0
/proc/16572/statm: 2385 1702 362 142 0 1339 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 9540

[startup+0.70165 s]
/proc/loadavg: 2.00 2.01 2.04 4/81 16572
/proc/meminfo: memFree=1358032/2055920 swapFree=4192812/4192956
[pid=16572] ppid=16570 vsize=14432 CPUtime=0.67
/proc/16572/stat : 16572 (pcs.small) R 16570 16572 16386 0 -1 4194304 4019 3860 0 0 63 1 1 2 25 0 1 0 58270202 14778368 2882 996147200 134512640 135095119 4294956304 18446744073709551615 134944166 0 0 4096 0 0 0 0 17 1 0 0
/proc/16572/statm: 3608 2882 375 142 0 2562 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 14432

Solver just ended. Dumping a history of the last processes samples

[startup+0.801664 s]
/proc/loadavg: 2.00 2.01 2.04 4/81 16572
/proc/meminfo: memFree=1358032/2055920 swapFree=4192812/4192956
[pid=16572] ppid=16570 vsize=13756 CPUtime=0.77
/proc/16572/stat : 16572 (pcs.small) R 16570 16572 16386 0 -1 4194304 4149 3860 0 0 73 1 1 2 25 0 1 0 58270202 14086144 2783 996147200 134512640 135095119 4294956304 18446744073709551615 134617027 0 0 4096 0 0 0 0 17 1 0 0
/proc/16572/statm: 3439 2783 389 142 0 2393 0
Current children cumulated CPU time (s) 0.77
Current children cumulated vsize (KiB) 13756

Child status: 0
Real time (s): 0.812065
CPU time (s): 0.797878
CPU user time (s): 0.762884
CPU system time (s): 0.034994
CPU usage (%): 98.253
Max. virtual memory (cumulated for all children) (KiB): 14432

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

runsolver used 0.004999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node37 at 2009-07-16 04:41:00
IDJOB=2073552
IDBENCH=55989
IDSOLVER=734
FILE ID=node37/2073552-1247712060
PBS_JOBID= 9521431
Free space on /tmp= 66392 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/bddSmall/normalized-bdd-21-133-18-78-25_ext.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2073552-1247712060/watcher-2073552-1247712060 -o /tmp/evaluation-result-2073552-1247712060/solver-2073552-1247712060 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 122529042 HOME/instance-2073552-1247712060.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 3ae432f57037edf38a55627c9dd43e63
RANDOM SEED=122529042

node37.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.260
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.260
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:       1358512 kB
Buffers:         83248 kB
Cached:         415872 kB
SwapCached:          0 kB
Active:         287724 kB
Inactive:       321836 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1358512 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3760 kB
Writeback:           0 kB
Mapped:         130816 kB
Slab:            72860 kB
Committed_AS:   719772 kB
PageTables:       2004 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= 66392 MiB
End job on node37 at 2009-07-16 04:41:01