Trace number 1055305

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.021995 0.0242499

DiagnosticValue
ASSIGNMENTS68
CHECKS18956

General information on the benchmark

Namecsp/jobShop-e0ddr1/
normalized-e0ddr1-10-by-5-2.xml
MD5SUM4eb8f99621b454ba27d9f51e4d6a63a3
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.021995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size118
Number of constraints which are defined in extension0
Number of constraints which are defined in intension265
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	c mistral-option version 1.313
0.00/0.02	s SATISFIABLE
0.00/0.02	v 109 115 126 134 144 88 98 106 116 146 60 64 92 126 137 28 65 71 81 84 19 30 40 60 127 10 37 56 73 106 1 4 15 64 86 13 18 27 43 53 62 72 81 92 101 90 98 114 138 144
0.00/0.02	d CHECKS 18956
0.00/0.02	d ASSIGNMENTS 68

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-1055305-1215059372/watcher-1055305-1215059372 -o /tmp/evaluation-result-1055305-1215059372/solver-1055305-1215059372 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1055305-1215059372.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: 2.00 2.01 2.00 3/80 24650
/proc/meminfo: memFree=1609048/2055920 swapFree=4191676/4192956
[pid=24650] ppid=24648 vsize=4584 CPUtime=0
/proc/24650/stat : 24650 (xsolve) R 24648 24650 24063 0 -1 4194304 337 0 0 0 0 0 0 0 18 0 1 0 117932499 4694016 304 996147200 134512640 135239763 4294956208 18446744073709551615 4159694800 0 0 4096 0 0 0 0 17 1 0 0
/proc/24650/statm: 1146 313 267 177 0 49 0

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

Child status: 0
Real time (s): 0.0242499
CPU time (s): 0.021995
CPU user time (s): 0.014997
CPU system time (s): 0.006998
CPU usage (%): 90.7012
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.014997
system time used= 0.006998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 779
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= 0

runsolver used 0.003999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node63 at 2008-07-03 06:29:32
IDJOB=1055305
IDBENCH=56813
IDSOLVER=357
FILE ID=node63/1055305-1215059372
PBS_JOBID= 7875191
Free space on /tmp= 66508 MiB

SOLVER NAME= Mistral-option 1.314
BENCH NAME= CPAI08/csp/jobShop-e0ddr1/normalized-e0ddr1-10-by-5-2.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-1055305-1215059372/watcher-1055305-1215059372 -o /tmp/evaluation-result-1055305-1215059372/solver-1055305-1215059372 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1055305-1215059372.xml -heu dyn -sac 3 -ds 2 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 4eb8f99621b454ba27d9f51e4d6a63a3
RANDOM SEED=1559853574

node63.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.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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1609464 kB
Buffers:          8724 kB
Cached:         135788 kB
SwapCached:        260 kB
Active:         356052 kB
Inactive:        34816 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1609464 kB
SwapTotal:     4192956 kB
SwapFree:      4191676 kB
Dirty:            1384 kB
Writeback:           0 kB
Mapped:         267648 kB
Slab:            40540 kB
Committed_AS:  1073472 kB
PageTables:       2104 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66508 MiB
End job on node63 at 2008-07-03 06:29:32