Trace number 1132138

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.037993 0.148202

DiagnosticValue
ASSIGNMENTS95
CHECKS4624

General information on the benchmark

Namecsp/CabinetStart1/
normalized-cabinet-5595.xml
MD5SUMb6df554c9a344850fb0cf62ab4c4cf20
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.025995
Satisfiable
(Un)Satisfiability was proved
Number of variables120
Number of constraints126
Maximum constraint arity15
Maximum domain size84591
Number of constraints which are defined in extension0
Number of constraints which are defined in intension21
Global constraints used (with number of constraints)element(98),weightedsum(7)

Solver Data (download as text)

0.00/0.09	c mistral-option version 1.313
0.00/0.14	s SATISFIABLE
0.00/0.14	v 2 1 6 2 7 7 3 4 3 4 5 6 3 6 0 5460 0 0 0 0 0 0 0 0 0 0 0 0 1610 0 0 3850 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3360 0 880 0 0 0 1000 0 0 0 0 0 0 0 0 3900 0 1680 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5500 0 0 0 0 0 2380 0 0 0 0 0 0 0 0 1000 0 2070 0 0 0 0 3200 2240 0 0 0 0 0 0 0 0 5460 5460 5240 5580 5500 5450 5440 5580
0.00/0.14	d CHECKS 4624
0.00/0.14	d ASSIGNMENTS 95

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-1132138-1220284671/watcher-1132138-1220284671 -o /tmp/evaluation-result-1132138-1220284671/solver-1132138-1220284671 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1132138-1220284671.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: 1.00 1.00 1.00 3/69 12670
/proc/meminfo: memFree=1144472/2055920 swapFree=4179820/4192956
[pid=12670] ppid=12668 vsize=820 CPUtime=0
/proc/12670/stat : 12670 (xsolve) R 12668 12670 12613 0 -1 4194304 39 0 0 0 0 0 0 0 18 0 1 0 355552011 839680 25 996147200 134512640 135239763 4294956192 18446744073709551615 4043556 0 0 4096 0 0 0 0 17 0 0 0
/proc/12670/statm: 205 25 19 177 0 3 0

[startup+0.0124391 s]
/proc/loadavg: 1.00 1.00 1.00 3/69 12670
/proc/meminfo: memFree=1144472/2055920 swapFree=4179820/4192956
[pid=12670] ppid=12668 vsize=820 CPUtime=0
/proc/12670/stat : 12670 (xsolve) R 12668 12670 12613 0 -1 4194304 39 0 0 0 0 0 0 0 18 0 1 0 355552011 839680 25 996147200 134512640 135239763 4294956192 18446744073709551615 4043323 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/12670/statm: 205 25 19 177 0 3 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 820

[startup+0.101087 s]
/proc/loadavg: 1.00 1.00 1.00 3/69 12670
/proc/meminfo: memFree=1144472/2055920 swapFree=4179820/4192956
[pid=12670] ppid=12668 vsize=5792 CPUtime=0
/proc/12670/stat : 12670 (xsolve) R 12668 12670 12613 0 -1 4194304 745 0 8 0 0 0 0 0 18 0 1 0 355552011 5931008 719 996147200 134512640 135239763 4294956192 18446744073709551615 134926154 0 0 4096 0 0 0 0 17 1 0 0
/proc/12670/statm: 1448 724 353 177 0 351 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5792

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

Child status: 0
Real time (s): 0.148202
CPU time (s): 0.037993
CPU user time (s): 0.022996
CPU system time (s): 0.014997
CPU usage (%): 25.6359
Max. virtual memory (cumulated for all children) (KiB): 5792

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.022996
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2075
page faults= 9
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 34
involuntary context switches= 8

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node92 at 2008-09-01 17:57:52
IDJOB=1132138
IDBENCH=66150
IDSOLVER=357
FILE ID=node92/1132138-1220284671
PBS_JOBID= 8108530
Free space on /tmp= 66564 MiB

SOLVER NAME= Mistral-option 1.314
BENCH NAME= CPAI08/csp/CabinetStart1/normalized-cabinet-5595.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-1132138-1220284671/watcher-1132138-1220284671 -o /tmp/evaluation-result-1132138-1220284671/solver-1132138-1220284671 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1132138-1220284671.xml -heu dyn -sac 3 -ds 2 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= b6df554c9a344850fb0cf62ab4c4cf20
RANDOM SEED=857020516

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.265
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.265
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:       1145656 kB
Buffers:         24588 kB
Cached:         825272 kB
SwapCached:       7008 kB
Active:          36452 kB
Inactive:       822572 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1145656 kB
SwapTotal:     4192956 kB
SwapFree:      4179820 kB
Dirty:            1028 kB
Writeback:           0 kB
Mapped:          14812 kB
Slab:            36696 kB
Committed_AS:   353224 kB
PageTables:       1756 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= 66560 MiB
End job on node92 at 2008-09-01 17:57:52