Trace number 2082670

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.227964 0.240321

DiagnosticValue
ASSIGNMENTS10

General information on the benchmark

Namecsp/super-jobShop/
super-jobShop-ewddr2/normalized-super-jobShop-ewddr2-7.xml
MD5SUM3d212b518200a202089f2dda1551e6b0
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.227964
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints845
Maximum constraint arity2
Maximum domain size149
Number of constraints which are defined in extension0
Number of constraints which are defined in intension845
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.18/0.21	c Seed is 233092930
0.18/0.21	c Constructing HOME/instance-2082670-1247721447.xml  with 5015 constraints
0.18/0.21	c Solving 10 backtracks
0.18/0.23	s SATISFIABLE
0.18/0.23	c V0=0, V1=1, V2=5, V3=4, V4=21, V5=57, V6=68, V7=69, V8=83, V9=152, V10=0, V11=51, V12=57, V13=19, V14=66, V15=67, V16=76, V17=75, V18=91, V19=152, V20=13, V21=14, V22=20, V23=19, V24=29, V25=30, V26=45, V27=44, V28=51, V29=52, V30=26, V31=27, V32=39, V33=40, V34=45, V35=44, V36=66, V37=67, V38=72, V39=152, V40=28, V41=19, V42=33, V43=76, V44=87, V45=75, V46=99, V47=110, V48=129, V49=152, V50=33, V51=71, V52=82, V53=51, V54=112, V55=111, V56=128, V57=129, V58=137, V59=138, V60=9, V61=10, V62=58, V63=16, V64=99, V65=75, V66=111, V67=112, V68=118, V69=152, V70=0, V71=1, V72=5, V73=4, V74=9, V75=75, V76=89, V77=21, V78=105, V79=106, V80=95, V81=76, V82=107, V83=108, V84=145, V85=144, V86=154, V87=155, V88=166, V89=163, V90=6, V91=76, V92=80, V93=37, V94=128, V95=129, V96=164, V97=163, V98=175, V99=174, 
0.18/0.23	v 0 1 5 4 21 57 68 69 83 152 0 51 57 19 66 67 76 75 91 152 13 14 20 19 29 30 45 44 51 52 26 27 39 40 45 44 66 67 72 152 28 19 33 76 87 75 99 110 129 152 33 71 82 51 112 111 128 129 137 138 9 10 58 16 99 75 111 112 118 152 0 1 5 4 9 75 89 21 105 106 95 76 107 108 145 144 154 155 166 163 6 76 80 37 128 129 164 163 175 174 
0.18/0.23	d ASSIGNMENTS 10

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-2082670-1247721447/watcher-2082670-1247721447 -o /tmp/evaluation-result-2082670-1247721447/solver-2082670-1247721447 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 233092930 HOME/instance-2082670-1247721447.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.00 2.00 4/72 16449
/proc/meminfo: memFree=1375136/2055920 swapFree=4192812/4192956
[pid=16449] ppid=16447 vsize=5356 CPUtime=0
/proc/16449/stat : 16449 (pcssolve) R 16447 16449 15802 0 -1 4194304 290 0 0 0 0 0 0 0 23 0 1 0 59211609 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 4466870 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/16449/statm: 1339 241 200 169 0 50 0
[pid=16450] ppid=16449 vsize=0 CPUtime=0
/proc/16450/stat : 16450 (fgrep) Z 16449 16449 15802 0 -1 4194316 155 0 0 0 0 0 0 0 24 0 1 0 59211610 0 0 996147200 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 1 0 0
/proc/16450/statm: 0 0 0 0 0 0 0

[startup+0.0148791 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16449
/proc/meminfo: memFree=1375136/2055920 swapFree=4192812/4192956
[pid=16449] ppid=16447 vsize=5356 CPUtime=0
/proc/16449/stat : 16449 (pcssolve) R 16447 16449 15802 0 -1 4194304 339 317 0 0 0 0 0 0 25 0 1 0 59211609 5484544 242 996147200 4194304 4889804 548682068800 18446744073709551615 269757244228 0 65536 4100 65538 0 0 0 17 1 0 0
/proc/16449/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.101896 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16449
/proc/meminfo: memFree=1375136/2055920 swapFree=4192812/4192956
[pid=16449] ppid=16447 vsize=7032 CPUtime=0.08
/proc/16449/stat : 16449 (pcs.big) R 16447 16449 15802 0 -1 4194304 1481 661 0 0 8 0 0 0 18 0 1 0 59211609 7200768 996 996147200 134512640 135215973 4294956304 18446744073709551615 134590947 0 0 4096 0 0 0 0 17 1 0 0
/proc/16449/statm: 1758 996 404 171 0 683 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7032

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

[startup+0.201908 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16449
/proc/meminfo: memFree=1375136/2055920 swapFree=4192812/4192956
[pid=16449] ppid=16447 vsize=9648 CPUtime=0.18
/proc/16449/stat : 16449 (pcs.big) R 16447 16449 15802 0 -1 4194304 2338 661 0 0 17 1 0 0 18 0 1 0 59211609 9879552 1486 996147200 134512640 135215973 4294956304 18446744073709551615 134583202 0 0 4096 0 0 0 0 17 1 0 0
/proc/16449/statm: 2412 1486 408 171 0 1337 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 9648

Child status: 0
Real time (s): 0.240321
CPU time (s): 0.227964
CPU user time (s): 0.210967
CPU system time (s): 0.016997
CPU usage (%): 94.8581
Max. virtual memory (cumulated for all children) (KiB): 9648

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

runsolver used 0.004999 second user time and 0.003999 second system time

The end

Launcher Data

Begin job on node13 at 2009-07-16 07:17:27
IDJOB=2082670
IDBENCH=57616
IDSOLVER=733
FILE ID=node13/2082670-1247721447
PBS_JOBID= 9521447
Free space on /tmp= 66308 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/super-jobShop/super-jobShop-ewddr2/normalized-super-jobShop-ewddr2-7.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2082670-1247721447/watcher-2082670-1247721447 -o /tmp/evaluation-result-2082670-1247721447/solver-2082670-1247721447 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 233092930 HOME/instance-2082670-1247721447.xml

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

MD5SUM BENCH= 3d212b518200a202089f2dda1551e6b0
RANDOM SEED=233092930

node13.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.241
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.241
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:       1375616 kB
Buffers:         83904 kB
Cached:         363468 kB
SwapCached:          0 kB
Active:         321232 kB
Inactive:       276860 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1375616 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1848 kB
Writeback:           0 kB
Mapped:         162236 kB
Slab:            67128 kB
Committed_AS:   641468 kB
PageTables:       2128 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= 66308 MiB
End job on node13 at 2009-07-16 07:17:27