Trace number 455535

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, and are wall clock time (not CPU 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 NameAnswerObjective functionCPU timeWall clock time
bsolo 3.0.16OPT-3 0.019996 0.0223921

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/bsg/normalized-bsg_10_4_1.opb
MD5SUM2f2a65bac822fb15bab629a6de652836
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark-3
Best CPU time to get the best result obtained on this benchmark0.007997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -3
Optimality of the best value was proved YES
Number of variables20
Total number of constraints31
Number of constraints which are clauses10
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints21
Minimum length of a constraint2
Maximum length of a constraint20
Number of terms in the objective function 10
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 10
Number of bits of the sum of numbers in the objective function 4
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 20
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)96
Sum of products size (including duplicates)192
Number of different products48
Sum of products size96

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00/0.00	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.00	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/455535-1178045239/instance-455535-1178045239.opb
0.00/0.00	c File size is 1770 bytes.
0.00/0.00	c Highest Coefficient sum: 20
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.002 s
0.00/0.00	c Var: 116 Constr: 224 106/22/96 Lit: 732 Watch. Lit: 618
0.00/0.00	c Obj. Vars: 10 (8.62069 % of total variables)
0.00/0.01	c Pre-processing Time: 0.008 s
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c        0    116      224      732    3      618     872      0      0 0.01
0.00/0.01	c Switching off LPR mode.
0.00/0.01	o -1	0.008
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c        0    116      225      742    3      621     879      1      0 0.01
0.00/0.01	o -2	0.009
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c        5    116      231      767    3      635     882      7    555 0.01
0.00/0.01	o -3	0.009
0.00/0.02	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.02	c       16    116      243      907    3      662     885     19   1777 0.01
0.00/0.02	c      116     75      343     1945    5      859     974    119   8923 0.01
0.00/0.02	v x1 -x2 -x3 -x4 -x5 -x6 x7 x8 -x9 -x10 -x14 -x17 -x18 -x16 -x13 -x15 x19 -x11 x12 x20
0.00/0.02	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.02	c    4      243     18      486      470     2964    246  14294 0.02
0.00/0.02	c Objective: -3
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	c Total time: 0.017 s

Verifier Data (download as text)

OK	-3

Watcher Data (download as text)

runsolver version 3.2.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node39/watcher-455535-1178045239 -o ROOT/results/node39/solver-455535-1178045239 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/455535-1178045239/instance-455535-1178045239.opb 

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): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.12 1.09 1.09 3/77 30496
/proc/meminfo: memFree=1833216/2055920 swapFree=4159404/4192956
[pid=30496] ppid=30494 vsize=19552 CPUtime=0
/proc/30496/stat : 30496 (bsolo3.0.16) R 30494 30496 23094 0 -1 4194304 375 0 0 0 0 0 0 0 18 0 1 0 252435914 20021248 344 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 11527803 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30496/statm: 4888 345 290 324 0 3956 0

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

Child status: 0
Real time (s): 0.0223921
CPU time (s): 0.019996
CPU user time (s): 0.016997
CPU system time (s): 0.002999
CPU usage (%): 89.2993
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node39 on Tue May  1 18:47:19 UTC 2007

IDJOB= 455535
IDBENCH= 48270
IDSOLVER= 163
FILE ID= node39/455535-1178045239

PBS_JOBID= 4728440

Free space on /tmp= 66558 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/manquinho/bsg/normalized-bsg_10_4_1.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/455535-1178045239/instance-455535-1178045239.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node39/watcher-455535-1178045239 -o ROOT/results/node39/solver-455535-1178045239 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/455535-1178045239/instance-455535-1178045239.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  2f2a65bac822fb15bab629a6de652836

RANDOM SEED= 648559745

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node39.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.256
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.256
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:       1833624 kB
Buffers:         66916 kB
Cached:          55296 kB
SwapCached:      13720 kB
Active:          98408 kB
Inactive:        56716 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1833624 kB
SwapTotal:     4192956 kB
SwapFree:      4159404 kB
Dirty:            6812 kB
Writeback:           0 kB
Mapped:          34752 kB
Slab:            52360 kB
Committed_AS:  4321692 kB
PageTables:       2024 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= 66558 MiB

End job on node39 on Tue May  1 18:47:19 UTC 2007