Trace number 237318

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 NameAnswerCPU timeWall clock time
Mistral 2006-12-04SAT 0.695893 0.703624

General information on the benchmark

Nameos-gp/
gp10-01-1093.xml
MD5SUM0da9d135f457ed0a2622be4bd1d9f01f
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.327949
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1094
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1000
Global constraints used (with number of constraints)

Solver Data (download as text)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints........... 0.06
0.20	c Allocating memory
0.20	c 
0.20	c time limit = -1
0.20	c heuristic = dom/wdeg
0.20	c restart policy = No restart
0.20	c 
0.20	c Solving
0.20	c
0.68	s SATISFIABLE
0.68	v 1093 809 893 890 1070 878 364 382 0 1069 1068 0 464 967 603 479 1091 1092 1033 1065 642 1092 0 464 1032 887 861 894 1067 584 967 458 1082 600 1067 890 382 0 1062 1064 1063 670 1091 893 0 642 896 759 746 14 42 600 1068 584 610 0 1092 975 1029 42 41 711 479 1033 1021 41 0 970 809 7 6 878 1090 8 1017 1062 443 1029 970 1032 5 923 1092 896 5 692 887 893 364 0 1 604 746 1 337 603 8 1032 692 861 0
0.68	d          SAT      4144 BTS      0.54 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node12/watcher-237318-1168347448 -o ROOT/results/node12/solver-237318-1168347448 -C 1800 -M 900 /tmp/evaluation/237318-1168347448/mistral/bin/solver /tmp/evaluation/237318-1168347448/unknown.xml -v 1 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.96 2.00 2.00 3/94 7673
/proc/meminfo: memFree=1562496/2055920 swapFree=4160348/4192956
[pid=7672] ppid=7670 vsize=18540 CPUtime=0
/proc/7672/stat : 7672 (runsolver) R 7670 7672 6570 0 -1 4194368 16 0 0 0 0 0 0 0 21 0 1 0 183139922 18984960 279 18446744073709551615 4194304 4267372 548682069040 18446744073709551615 252429528359 0 0 4096 24578 0 0 0 17 1 0 0
/proc/7672/statm: 4635 279 244 17 0 2626 0

[startup+0.102345 s]
/proc/loadavg: 1.96 2.00 2.00 3/94 7673
/proc/meminfo: memFree=1562496/2055920 swapFree=4160348/4192956
[pid=7672] ppid=7670 vsize=13136 CPUtime=0.08
/proc/7672/stat : 7672 (solver) R 7670 7672 6570 0 -1 4194304 2361 0 0 0 8 0 0 0 18 0 1 0 183139922 13451264 2329 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4156460784 0 0 4096 0 0 0 0 17 1 0 0
/proc/7672/statm: 3284 2329 715 92 0 1628 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 13136

[startup+0.51241 s]
/proc/loadavg: 1.96 2.00 2.00 3/94 7673
/proc/meminfo: memFree=1562496/2055920 swapFree=4160348/4192956
[pid=7672] ppid=7670 vsize=23460 CPUtime=0.49
/proc/7672/stat : 7672 (solver) R 7670 7672 6570 0 -1 4194304 4971 0 0 0 48 1 0 0 22 0 1 0 183139922 24023040 4939 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134647033 0 0 4096 0 0 0 0 17 1 0 0
/proc/7672/statm: 5865 4939 718 92 0 4209 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 23460

Child status: 0
Real time (s): 0.703624
CPU time (s): 0.695893
CPU user time (s): 0.675897
CPU system time (s): 0.019996
CPU usage (%): 98.9012
Max. virtual memory (cumulated for all children) (KiB): 23460

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

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node12 on Tue Jan  9 12:57:29 UTC 2007


IDJOB= 237318
IDBENCH= 6913
FILE ID= node12/237318-1168347448

PBS_JOBID= 3503206

Free space on /tmp= 66557 MiB

BENCH NAME= HOME/pub/bench/CPAI06/os-gp/gp10-01-1093.xml
COMMAND LINE= /tmp/evaluation/237318-1168347448/mistral/bin/solver /tmp/evaluation/237318-1168347448/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node12/watcher-237318-1168347448 -o ROOT/results/node12/solver-237318-1168347448 -C 1800 -M 900  /tmp/evaluation/237318-1168347448/mistral/bin/solver /tmp/evaluation/237318-1168347448/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  0da9d135f457ed0a2622be4bd1d9f01f

RANDOM SEED= 534939251

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1562976 kB
Buffers:         81424 kB
Cached:         266816 kB
SwapCached:       4816 kB
Active:         232488 kB
Inactive:       199688 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1562976 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:            3100 kB
Writeback:           0 kB
Mapped:         102344 kB
Slab:            45560 kB
Committed_AS:  6144464 kB
PageTables:       2284 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= 66557 MiB



End job on node12 on Tue Jan  9 12:57:30 UTC 2007