Trace number 2085850

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.022995 0.023665

DiagnosticValue
ASSIGNMENTS0

General information on the benchmark

Namecsp/graphColoring/insertion/k-insertion/
normalized-4-insertions-3-4.xml
MD5SUMce3da2ca24778425aa8006ff19819a18
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 benchmark0.019996
Satisfiable
(Un)Satisfiability was proved
Number of variables79
Number of constraints156
Maximum constraint arity2
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension156
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c small-domain mode
0.00/0.01	c Seed is 142467712
0.00/0.01	c Constructing HOME/instance-2085850-1247726484.xml  with 156 constraints
0.00/0.02	c Solving 0 backtracks
0.00/0.02	s SATISFIABLE
0.00/0.02	c V0=0, V1=1, V2=0, V3=2, V4=1, V5=1, V6=0, V7=0, V8=1, V9=1, V10=0, V11=0, V12=1, V13=0, V14=1, V15=0, V16=2, V17=1, V18=1, V19=0, V20=0, V21=1, V22=1, V23=0, V24=0, V25=1, V26=0, V27=1, V28=0, V29=2, V30=1, V31=1, V32=0, V33=0, V34=1, V35=1, V36=0, V37=0, V38=1, V39=0, V40=1, V41=0, V42=2, V43=1, V44=1, V45=0, V46=0, V47=1, V48=1, V49=0, V50=0, V51=1, V52=0, V53=1, V54=0, V55=3, V56=1, V57=1, V58=0, V59=0, V60=1, V61=1, V62=0, V63=0, V64=1, V65=2, V66=1, V67=2, V68=2, V69=1, V70=1, V71=2, V72=2, V73=1, V74=1, V75=2, V76=2, V77=1, V78=0, 
0.00/0.02	v 0 1 0 2 1 1 0 0 1 1 0 0 1 0 1 0 2 1 1 0 0 1 1 0 0 1 0 1 0 2 1 1 0 0 1 1 0 0 1 0 1 0 2 1 1 0 0 1 1 0 0 1 0 1 0 3 1 1 0 0 1 1 0 0 1 2 1 2 2 1 1 2 2 1 1 2 2 1 0 
0.00/0.02	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-2085850-1247726484/watcher-2085850-1247726484 -o /tmp/evaluation-result-2085850-1247726484/solver-2085850-1247726484 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 142467712 HOME/instance-2085850-1247726484.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.03 2.00 2.00 4/82 16951
/proc/meminfo: memFree=1496264/2055920 swapFree=4192812/4192956
[pid=16951] ppid=16949 vsize=5356 CPUtime=0
/proc/16951/stat : 16951 (pcssolve) S 16949 16951 16586 0 -1 4194304 305 0 0 0 0 0 0 0 18 0 1 0 59713337 5484544 242 996147200 4194304 4889804 548682068800 18446744073709551615 224264774468 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/16951/statm: 1339 242 201 169 0 50 0
[pid=16952] ppid=16951 vsize=5356 CPUtime=0
/proc/16952/stat : 16952 (pcssolve) R 16951 16951 16586 0 -1 4194368 22 0 0 0 0 0 0 0 19 0 1 0 59713337 5484544 243 996147200 4194304 4889804 548682068800 18446744073709551615 224264776999 0 0 4096 0 0 0 0 17 1 0 0
/proc/16952/statm: 1339 243 202 169 0 50 0
[pid=16953] ppid=16951 vsize=3676 CPUtime=0
/proc/16953/stat : 16953 (grep) S 16951 16951 16586 0 -1 4194304 154 0 0 0 0 0 0 0 18 0 1 0 59713338 3764224 121 996147200 4194304 4274172 548682069040 18446744073709551615 224264945746 0 0 4096 0 18446744071563648864 0 0 17 0 0 0
/proc/16953/statm: 919 121 99 19 0 43 0

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

Child status: 0
Real time (s): 0.023665
CPU time (s): 0.022995
CPU user time (s): 0.006998
CPU system time (s): 0.015997
CPU usage (%): 97.1688
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.006998
system time used= 0.015997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1649
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= 12

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node82 at 2009-07-16 08:41:24
IDJOB=2085850
IDBENCH=58521
IDSOLVER=734
FILE ID=node82/2085850-1247726484
PBS_JOBID= 9521606
Free space on /tmp= 66316 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/graphColoring/insertion/k-insertion/normalized-4-insertions-3-4.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2085850-1247726484/watcher-2085850-1247726484 -o /tmp/evaluation-result-2085850-1247726484/solver-2085850-1247726484 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 142467712 HOME/instance-2085850-1247726484.xml

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

MD5SUM BENCH= ce3da2ca24778425aa8006ff19819a18
RANDOM SEED=142467712

node82.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.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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1496744 kB
Buffers:         78728 kB
Cached:         349876 kB
SwapCached:          0 kB
Active:          87612 kB
Inactive:       384712 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1496744 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2548 kB
Writeback:           0 kB
Mapped:          64188 kB
Slab:            71940 kB
Committed_AS:   579984 kB
PageTables:       1900 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66312 MiB
End job on node82 at 2009-07-16 08:41:24