Trace number 1098850

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
Mistral-option 1.314SAT 0.063989 0.144839

DiagnosticValue
ASSIGNMENTS615
CHECKS183207

General information on the benchmark

Namecsp/rand-2-30-15/
normalized-rand-2-30-15-306-230-5_ext.xml
MD5SUMec15930c749c78e639f3a37e785f6887
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.063989
Satisfiable
(Un)Satisfiability was proved
Number of variables30
Number of constraints220
Maximum constraint arity2
Maximum domain size15
Number of constraints which are defined in extension220
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c mistral-option version 1.313
0.02/0.14	s SATISFIABLE
0.02/0.14	v 7 5 12 10 4 3 2 5 8 0 9 1 9 2 6 1 0 4 4 14 7 10 0 2 0 4 8 12 13 4
0.02/0.14	d CHECKS 183207
0.02/0.14	d ASSIGNMENTS 615

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1098850-1215285523/watcher-1098850-1215285523 -o /tmp/evaluation-result-1098850-1215285523/solver-1098850-1215285523 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1098850-1215285523.xml -heu dyn -sac 3 -ds 2 

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): 2200 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
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: 3.08 3.01 3.00 6/82 5411
/proc/meminfo: memFree=1715160/2055920 swapFree=3921008/4192956
[pid=5411] ppid=5409 vsize=4588 CPUtime=0
/proc/5411/stat : 5411 (xsolve) R 5409 5411 3145 0 -1 4194304 433 0 0 0 0 0 0 0 19 0 1 0 651478178 4698112 399 996147200 134512640 135239763 4294956192 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 0 0 0
/proc/5411/statm: 1147 403 349 177 0 50 0

[startup+0.0984169 s]
/proc/loadavg: 3.08 3.01 3.00 6/82 5411
/proc/meminfo: memFree=1715160/2055920 swapFree=3921008/4192956
[pid=5411] ppid=5409 vsize=5248 CPUtime=0.02
/proc/5411/stat : 5411 (xsolve) R 5409 5411 3145 0 -1 4194304 650 0 0 0 2 0 0 0 19 0 1 0 651478178 5373952 616 996147200 134512640 135239763 4294956192 18446744073709551615 134789553 0 0 4096 0 0 0 0 17 0 0 0
/proc/5411/statm: 1312 616 392 177 0 215 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5248

[startup+0.101415 s]
/proc/loadavg: 3.08 3.01 3.00 6/82 5411
/proc/meminfo: memFree=1715160/2055920 swapFree=3921008/4192956
[pid=5411] ppid=5409 vsize=5248 CPUtime=0.02
/proc/5411/stat : 5411 (xsolve) R 5409 5411 3145 0 -1 4194304 650 0 0 0 2 0 0 0 19 0 1 0 651478178 5373952 616 996147200 134512640 135239763 4294956192 18446744073709551615 134789553 0 0 4096 0 0 0 0 17 0 0 0
/proc/5411/statm: 1312 616 392 177 0 215 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5248

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

Child status: 0
Real time (s): 0.144839
CPU time (s): 0.063989
CPU user time (s): 0.06099
CPU system time (s): 0.002999
CPU usage (%): 44.1794
Max. virtual memory (cumulated for all children) (KiB): 5248

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.06099
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= 667
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= 7
involuntary context switches= 7

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node92 at 2008-07-05 21:18:43
IDJOB=1098850
IDBENCH=59664
IDSOLVER=357
FILE ID=node92/1098850-1215285523
PBS_JOBID= 7882270
Free space on /tmp= 66452 MiB

SOLVER NAME= Mistral-option 1.314
BENCH NAME= CPAI08/csp/rand-2-30-15/normalized-rand-2-30-15-306-230-5_ext.xml
COMMAND LINE= HOME/xsolve BENCHNAME -heu dyn -sac 3 -ds 2 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1098850-1215285523/watcher-1098850-1215285523 -o /tmp/evaluation-result-1098850-1215285523/solver-1098850-1215285523 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1098850-1215285523.xml -heu dyn -sac 3 -ds 2 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= ec15930c749c78e639f3a37e785f6887
RANDOM SEED=871050630

node92.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.223
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.223
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:       1715640 kB
Buffers:         43544 kB
Cached:         186564 kB
SwapCached:       7076 kB
Active:         187216 kB
Inactive:        94496 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1715640 kB
SwapTotal:     4192956 kB
SwapFree:      3921008 kB
Dirty:            1600 kB
Writeback:           0 kB
Mapped:          59248 kB
Slab:            42520 kB
Committed_AS:  1544080 kB
PageTables:       2984 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= 66452 MiB
End job on node92 at 2008-07-05 21:18:44