Trace number 1052821

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-prime 1.313SAT 0.010997 0.018828

DiagnosticValue
ASSIGNMENTS14
CHECKS2724

General information on the benchmark

Namecsp/aim-50/
normalized-aim-50-6-0-sat-4_ext.xml
MD5SUMe7463865184f91144af9492a7dc22538
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.010997
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints273
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension273
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.01	c mistral-prime version 1.313
0.00/0.01	s SATISFIABLE
0.00/0.01	v 0 0 1 1 0 1 1 0 1 1 0 1 0 1 1 1 0 1 0 1 1 1 1 0 0 1 1 0 1 1 1 1 0 0 0 0 1 1 0 1 0 1 1 1 0 0 0 0 0 1
0.00/0.01	d CHECKS 2724
0.00/0.01	d ASSIGNMENTS 14

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-1052821-1215057371/watcher-1052821-1215057371 -o /tmp/evaluation-result-1052821-1215057371/solver-1052821-1215057371 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1052821-1215057371.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): 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.92 1.98 1.99 4/81 12507
/proc/meminfo: memFree=1447416/2055920 swapFree=4180288/4192956
[pid=12507] ppid=12505 vsize=18572 CPUtime=0
/proc/12507/stat : 12507 (runsolver) R 12505 12507 9024 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 411354442 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 224627584295 0 0 4096 24578 0 0 0 17 1 0 0
/proc/12507/statm: 4643 292 257 25 0 2626 0

[startup+0.00767207 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 12507
/proc/meminfo: memFree=1447416/2055920 swapFree=4180288/4192956
[pid=12507] ppid=12505 vsize=2288 CPUtime=0
/proc/12507/stat : 12507 (xsolve) D 12505 12507 9024 0 -1 4194304 63 0 0 0 0 0 0 0 18 0 1 0 411354442 2342912 47 996147200 134512640 135237403 4294956256 18446744073709551615 3810084 0 2147483391 4096 0 18446744072099937270 0 0 17 1 0 0
/proc/12507/statm: 808 52 38 176 0 12 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2288

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

[startup+0.00767207 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 12507
/proc/meminfo: memFree=1447416/2055920 swapFree=4180288/4192956
[pid=12507] ppid=12505 vsize=2288 CPUtime=0
/proc/12507/stat : 12507 (xsolve) D 12505 12507 9024 0 -1 4194304 63 0 0 0 0 0 0 0 18 0 1 0 411354442 2342912 47 996147200 134512640 135237403 4294956256 18446744073709551615 3810084 0 2147483391 4096 0 18446744072099937270 0 0 17 1 0 0
/proc/12507/statm: 808 52 38 176 0 12 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2288

Child status: 0
Real time (s): 0.018828
CPU time (s): 0.010997
CPU user time (s): 0.008998
CPU system time (s): 0.001999
CPU usage (%): 58.4078
Max. virtual memory (cumulated for all children) (KiB): 2288

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.008998
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 541
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.002999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node49 at 2008-07-03 05:56:11
IDJOB=1052821
IDBENCH=56018
IDSOLVER=358
FILE ID=node49/1052821-1215057371
PBS_JOBID= 7875077
Free space on /tmp= 66336 MiB

SOLVER NAME= Mistral-prime 1.313
BENCH NAME= CPAI08/csp/aim-50/normalized-aim-50-6-0-sat-4_ext.xml
COMMAND LINE= HOME/xsolve BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1052821-1215057371/watcher-1052821-1215057371 -o /tmp/evaluation-result-1052821-1215057371/solver-1052821-1215057371 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1052821-1215057371.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= e7463865184f91144af9492a7dc22538
RANDOM SEED=2127137512

node49.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.249
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.249
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:       1447896 kB
Buffers:         41172 kB
Cached:         354588 kB
SwapCached:       6120 kB
Active:         353584 kB
Inactive:       187672 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1447896 kB
SwapTotal:     4192956 kB
SwapFree:      4180288 kB
Dirty:           26204 kB
Writeback:           0 kB
Mapped:         158844 kB
Slab:            51556 kB
Committed_AS:  1473972 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= 66336 MiB
End job on node49 at 2008-07-03 05:56:11