Trace number 2088709

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 0.3.2SAT 0.169973 0.183311

DiagnosticValue
ASSIGNMENTS106

General information on the benchmark

Namecsp/geom/
normalized-geo50-20-d4-75-26_ext.xml
MD5SUM5c4e18ab9bb84761c68492825d16695e
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.05699
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints399
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension399
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c small-domain mode
0.00/0.02	c Seed is 1687074569
0.00/0.02	c Constructing HOME/instance-2088709-1247729463.xml  with 7949 constraints
0.07/0.12	c Solving 106 backtracks 3 restarts
0.07/0.18	s SATISFIABLE
0.07/0.18	c V0=19, V1=8, V2=7, V3=2, V4=4, V5=15, V6=16, V7=3, V8=1, V9=17, V10=15, V11=20, V12=3, V13=7, V14=19, V15=13, V16=17, V17=14, V18=3, V19=16, V20=9, V21=14, V22=17, V23=10, V24=18, V25=11, V26=4, V27=19, V28=4, V29=19, V30=5, V31=6, V32=3, V33=19, V34=16, V35=1, V36=13, V37=4, V38=20, V39=7, V40=8, V41=8, V42=13, V43=9, V44=20, V45=10, V46=17, V47=20, V48=8, V49=1, 
0.07/0.18	v 19 8 7 2 4 15 16 3 1 17 15 20 3 7 19 13 17 14 3 16 9 14 17 10 18 11 4 19 4 19 5 6 3 19 16 1 13 4 20 7 8 8 13 9 20 10 17 20 8 1 
0.07/0.18	d ASSIGNMENTS 106

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-2088709-1247729463/watcher-2088709-1247729463 -o /tmp/evaluation-result-2088709-1247729463/solver-2088709-1247729463 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1687074569 HOME/instance-2088709-1247729463.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: 1.92 1.99 1.99 4/81 18010
/proc/meminfo: memFree=1322960/2055920 swapFree=4191900/4192956
[pid=18010] ppid=18008 vsize=18576 CPUtime=0
/proc/18010/stat : 18010 (runsolver) R 18008 18010 17549 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 60013121 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 240472616231 0 0 4096 24578 0 0 0 17 1 0 0
/proc/18010/statm: 4644 284 249 26 0 2626 0

[startup+0.0257731 s]
/proc/loadavg: 1.92 1.99 1.99 4/81 18010
/proc/meminfo: memFree=1322960/2055920 swapFree=4191900/4192956
[pid=18010] ppid=18008 vsize=2772 CPUtime=0
/proc/18010/stat : 18010 (pcs.small) R 18008 18010 17549 0 -1 4194304 411 822 0 0 0 0 0 0 22 0 1 0 60013121 2838528 35 996147200 134512640 135095119 4294956304 18446744073709551615 7512868 0 0 4096 0 0 0 0 17 0 0 0
/proc/18010/statm: 693 35 25 142 0 10 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2772

[startup+0.10281 s]
/proc/loadavg: 1.92 1.99 1.99 4/81 18010
/proc/meminfo: memFree=1322960/2055920 swapFree=4191900/4192956
[pid=18010] ppid=18008 vsize=5696 CPUtime=0.07
/proc/18010/stat : 18010 (pcs.small) R 18008 18010 17549 0 -1 4194304 1140 822 0 0 7 0 0 0 22 0 1 0 60013121 5832704 749 996147200 134512640 135095119 4294956304 18446744073709551615 4159337025 0 0 4096 0 0 0 0 17 0 0 0
/proc/18010/statm: 1424 749 364 142 0 378 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5696

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

Child status: 0
Real time (s): 0.183311
CPU time (s): 0.169973
CPU user time (s): 0.158975
CPU system time (s): 0.010998
CPU usage (%): 92.7238
Max. virtual memory (cumulated for all children) (KiB): 5696

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.158975
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2261
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= 22
involuntary context switches= 15

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node15 at 2009-07-16 09:31:03
IDJOB=2088709
IDBENCH=58973
IDSOLVER=733
FILE ID=node15/2088709-1247729463
PBS_JOBID= 9521504
Free space on /tmp= 66300 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/geom/normalized-geo50-20-d4-75-26_ext.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2088709-1247729463/watcher-2088709-1247729463 -o /tmp/evaluation-result-2088709-1247729463/solver-2088709-1247729463 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1687074569 HOME/instance-2088709-1247729463.xml

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

MD5SUM BENCH= 5c4e18ab9bb84761c68492825d16695e
RANDOM SEED=1687074569

node15.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.220
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.220
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:       1323448 kB
Buffers:         90716 kB
Cached:         511960 kB
SwapCached:        416 kB
Active:         249360 kB
Inactive:       413624 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1323448 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            1968 kB
Writeback:           0 kB
Mapped:          79960 kB
Slab:            54416 kB
Committed_AS:   902764 kB
PageTables:       2028 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= 66300 MiB
End job on node15 at 2009-07-16 09:31:03