Trace number 2065577

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.185971 0.189797

DiagnosticValue
ASSIGNMENTS27

General information on the benchmark

Namecsp/primes-30/
normalized-primes-30-80-2-7.xml
MD5SUMe8c315bcbe0748e0a375ad8d37a916fb
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.029995
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints80
Maximum constraint arity9
Maximum domain size112
Number of constraints which are defined in extension0
Number of constraints which are defined in intension80
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 204990365
0.00/0.01	c Constructing HOME/instance-2065577-1247703577.xml  with 868 constraints
0.00/0.04	c Solving 27 backtracks 1 restarts
0.08/0.18	s SATISFIABLE
0.08/0.18	c V0=43, V1=59, V2=107, V3=101, V4=89, V5=101, V6=59, V7=41, V8=29, V9=3, V10=5, V11=19, V12=73, V13=71, V14=89, V15=59, V16=2, V17=17, V18=83, V19=59, V20=37, V21=23, V22=107, V23=29, V24=5, V25=73, V26=5, V27=43, V28=19, V29=101, V30=113, V31=41, V32=41, V33=67, V34=113, V35=107, V36=43, V37=59, V38=3, V39=83, V40=29, V41=7, V42=79, V43=113, V44=47, V45=19, V46=23, V47=47, V48=13, V49=2, V50=89, V51=59, V52=3, V53=73, V54=103, V55=7, V56=5, V57=73, V58=59, V59=3, V60=53, V61=53, V62=47, V63=107, V64=103, V65=13, V66=59, V67=29, V68=43, V69=61, V70=97, V71=53, V72=41, V73=53, V74=47, V75=107, V76=47, V77=47, V78=7, V79=73, V80=19, V81=67, V82=17, V83=23, V84=23, V85=97, V86=7, V87=37, V88=47, V89=71, V90=41, V91=2, V92=103, V93=67, V94=71, V95=83, V96=59, V97=17, V98=97, V99=113, 
0.08/0.18	v 43 59 107 101 89 101 59 41 29 3 5 19 73 71 89 59 2 17 83 59 37 23 107 29 5 73 5 43 19 101 113 41 41 67 113 107 43 59 3 83 29 7 79 113 47 19 23 47 13 2 89 59 3 73 103 7 5 73 59 3 53 53 47 107 103 13 59 29 43 61 97 53 41 53 47 107 47 47 7 73 19 67 17 23 23 97 7 37 47 71 41 2 103 67 71 83 59 17 97 113 
0.08/0.18	d ASSIGNMENTS 27

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-2065577-1247703577/watcher-2065577-1247703577 -o /tmp/evaluation-result-2065577-1247703577/solver-2065577-1247703577 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 204990365 HOME/instance-2065577-1247703577.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.91 1.99 2.01 4/72 11631
/proc/meminfo: memFree=1304816/2055920 swapFree=4192812/4192956
[pid=11631] ppid=11629 vsize=5356 CPUtime=0
/proc/11631/stat : 11631 (pcssolve) S 11629 11631 10131 0 -1 4194304 305 155 0 0 0 0 0 0 20 0 1 0 57423997 5484544 242 996147200 4194304 4889804 548682068800 18446744073709551615 233588712260 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/11631/statm: 1339 242 201 169 0 50 0
[pid=11633] ppid=11631 vsize=3676 CPUtime=0
/proc/11633/stat : 11633 (grep) R 11631 11631 10131 0 -1 4194304 129 0 0 0 0 0 0 0 22 0 1 0 57423997 3764224 96 996147200 4194304 4274172 548682069040 18446744073709551615 233588755424 0 0 4096 0 0 0 0 17 1 0 0
/proc/11633/statm: 919 96 78 19 0 43 0

[startup+0.0467531 s]
/proc/loadavg: 1.91 1.99 2.01 4/72 11631
/proc/meminfo: memFree=1304816/2055920 swapFree=4192812/4192956
[pid=11631] ppid=11629 vsize=5300 CPUtime=0.03
/proc/11631/stat : 11631 (pcs.big) R 11629 11631 10131 0 -1 4194304 1000 656 0 0 3 0 0 0 24 0 1 0 57423997 5427200 631 996147200 134512640 135215973 4294956304 18446744073709551615 134609888 0 0 4096 0 0 0 0 17 0 0 0
/proc/11631/statm: 1325 631 412 171 0 250 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5300

[startup+0.102766 s]
/proc/loadavg: 1.91 1.99 2.01 4/72 11631
/proc/meminfo: memFree=1304816/2055920 swapFree=4192812/4192956
[pid=11631] ppid=11629 vsize=6388 CPUtime=0.08
/proc/11631/stat : 11631 (pcs.big) R 11629 11631 10131 0 -1 4194304 1352 656 0 0 8 0 0 0 24 0 1 0 57423997 6541312 825 996147200 134512640 135215973 4294956304 18446744073709551615 134610629 0 0 4096 0 0 0 0 17 0 0 0
/proc/11631/statm: 1597 825 416 171 0 522 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 6388

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

Child status: 0
Real time (s): 0.189797
CPU time (s): 0.185971
CPU user time (s): 0.167974
CPU system time (s): 0.017997
CPU usage (%): 97.9842
Max. virtual memory (cumulated for all children) (KiB): 6388

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.167974
system time used= 0.017997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2517
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= 16
involuntary context switches= 19

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node27 at 2009-07-16 02:19:37
IDJOB=2065577
IDBENCH=54375
IDSOLVER=734
FILE ID=node27/2065577-1247703577
PBS_JOBID= 9521256
Free space on /tmp= 66244 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/primes-30/normalized-primes-30-80-2-7.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2065577-1247703577/watcher-2065577-1247703577 -o /tmp/evaluation-result-2065577-1247703577/solver-2065577-1247703577 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 204990365 HOME/instance-2065577-1247703577.xml

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

MD5SUM BENCH= e8c315bcbe0748e0a375ad8d37a916fb
RANDOM SEED=204990365

node27.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		: 2800.239
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	: 5521.40
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		: 2800.239
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:       1305232 kB
Buffers:         77544 kB
Cached:         557304 kB
SwapCached:          0 kB
Active:         264788 kB
Inactive:       411816 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1305232 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1972 kB
Writeback:           0 kB
Mapped:          53092 kB
Slab:            59436 kB
Committed_AS:   580648 kB
PageTables:       1744 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264948 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66244 MiB
End job on node27 at 2009-07-16 02:19:38