Trace number 2087686

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.290955 0.29456

DiagnosticValue
ASSIGNMENTS66

General information on the benchmark

Namecsp/os-taillard-7/
normalized-os-taillard-7-105-4.xml
MD5SUM4e57864601eb28e4f6a729744d322830
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.081986
Satisfiable
(Un)Satisfiability was proved
Number of variables49
Number of constraints294
Maximum constraint arity2
Maximum domain size434
Number of constraints which are defined in extension0
Number of constraints which are defined in intension294
Global constraints used (with number of constraints)

Solver Data

0.00/0.01	c has big domains
0.00/0.01	c big-domain mode
0.00/0.01	c Seed is 447959322
0.00/0.01	c Constructing HOME/instance-2087686-1247728228.xml  with 2058 constraints
0.03/0.04	c Solving 66 backtracks 2 restarts
0.18/0.29	s SATISFIABLE
0.18/0.29	c V0=0, V1=267, V2=175, V3=102, V4=197, V5=238, V6=357, V7=310, V8=378, V9=227, V10=74, V11=0, V12=235, V13=165, V14=318, V15=102, V16=322, V17=378, V18=215, V19=3, V20=155, V21=159, V22=71, V23=143, V24=36, V25=227, V26=389, V27=245, V28=133, V29=208, V30=17, V31=175, V32=356, V33=90, V34=261, V35=36, V36=141, V37=226, V38=375, V39=305, V40=0, V41=102, V42=302, V43=0, V44=294, V45=199, V46=90, V47=364, V48=258, 
0.18/0.29	v 0 267 175 102 197 238 357 310 378 227 74 0 235 165 318 102 322 378 215 3 155 159 71 143 36 227 389 245 133 208 17 175 356 90 261 36 141 226 375 305 0 102 302 0 294 199 90 364 258 
0.18/0.29	d ASSIGNMENTS 66

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-2087686-1247728228/watcher-2087686-1247728228 -o /tmp/evaluation-result-2087686-1247728228/solver-2087686-1247728228 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 447959322 HOME/instance-2087686-1247728228.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.98 1.99 4/82 15823
/proc/meminfo: memFree=1641328/2055920 swapFree=4192812/4192956
[pid=15823] ppid=15821 vsize=5356 CPUtime=0
/proc/15823/stat : 15823 (pcssolve) R 15821 15823 14642 0 -1 4194304 273 0 0 0 0 0 0 0 20 0 1 0 59888221 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 243665529503 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15823/statm: 1339 241 200 169 0 50 0
[pid=15824] ppid=15823 vsize=5356 CPUtime=0
/proc/15824/stat : 15824 (pcssolve) R 15823 15823 14642 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 59888222 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 243665529503 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15824/statm: 1339 241 200 169 0 50 0

[startup+0.047024 s]
/proc/loadavg: 1.92 1.98 1.99 4/82 15823
/proc/meminfo: memFree=1641328/2055920 swapFree=4192812/4192956
[pid=15823] ppid=15821 vsize=5340 CPUtime=0.03
/proc/15823/stat : 15823 (pcs.big) R 15821 15823 14642 0 -1 4194304 996 657 0 0 3 0 0 0 24 0 1 0 59888221 5468160 627 996147200 134512640 135215973 4294956304 18446744073709551615 7220756 0 0 4096 0 0 0 0 17 0 0 0
/proc/15823/statm: 1335 627 394 171 0 260 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5340

[startup+0.101033 s]
/proc/loadavg: 1.92 1.98 1.99 4/82 15823
/proc/meminfo: memFree=1641328/2055920 swapFree=4192812/4192956
[pid=15823] ppid=15821 vsize=5944 CPUtime=0.08
/proc/15823/stat : 15823 (pcs.big) R 15821 15823 14642 0 -1 4194304 1178 657 0 0 8 0 0 0 24 0 1 0 59888221 6086656 809 996147200 134512640 135215973 4294956304 18446744073709551615 134532897 0 0 4096 0 0 0 0 17 0 0 0
/proc/15823/statm: 1486 809 406 171 0 411 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5944

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

[startup+0.201053 s]
/proc/loadavg: 1.92 1.98 1.99 4/82 15823
/proc/meminfo: memFree=1641328/2055920 swapFree=4192812/4192956
[pid=15823] ppid=15821 vsize=6284 CPUtime=0.18
/proc/15823/stat : 15823 (pcs.big) R 15821 15823 14642 0 -1 4194304 1253 657 0 0 18 0 0 0 25 0 1 0 59888221 6434816 831 996147200 134512640 135215973 4294956304 18446744073709551615 134550961 0 0 4096 0 0 0 0 17 0 0 0
/proc/15823/statm: 1571 831 406 171 0 496 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 6284

Child status: 0
Real time (s): 0.29456
CPU time (s): 0.290955
CPU user time (s): 0.278957
CPU system time (s): 0.011998
CPU usage (%): 98.7761
Max. virtual memory (cumulated for all children) (KiB): 6284

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.278957
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1949
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= 11
involuntary context switches= 17

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data

Begin job on node84 at 2009-07-16 09:10:29
IDJOB=2087686
IDBENCH=58780
IDSOLVER=733
FILE ID=node84/2087686-1247728228
PBS_JOBID= 9521526
Free space on /tmp= 66184 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/os-taillard-7/normalized-os-taillard-7-105-4.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2087686-1247728228/watcher-2087686-1247728228 -o /tmp/evaluation-result-2087686-1247728228/solver-2087686-1247728228 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 447959322 HOME/instance-2087686-1247728228.xml

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

MD5SUM BENCH= 4e57864601eb28e4f6a729744d322830
RANDOM SEED=447959322

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1641808 kB
Buffers:         77472 kB
Cached:         215064 kB
SwapCached:          0 kB
Active:         118804 kB
Inactive:       206744 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1641808 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1812 kB
Writeback:           0 kB
Mapped:          53356 kB
Slab:            73772 kB
Committed_AS:   532368 kB
PageTables:       1832 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= 66180 MiB
End job on node84 at 2009-07-16 09:10:29