Trace number 2082898

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 1.545SAT 0.478926 0.485113

DiagnosticValue
ASSIGNMENTS801
CHECKS2699310
NODES801

General information on the benchmark

Namecsp/os-gp/
normalized-gp10-01-1093.xml
MD5SUM2960c39330e67b59bd11d1942a6cbea3
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.478926
Satisfiable
(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 

0.00/0.17	c mistral version 1.545
0.38/0.47	s SATISFIABLE
0.38/0.47	v 1093 809 903 900 1089 1090 364 382 0 1092 1078 0 1092 967 1062 495 1091 937 1069 1033 612 923 1 465 1002 1091 867 893 1060 585 937 458 0 600 1 890 382 4 1092 1078 1079 674 745 9 1091 689 893 759 746 0 12 600 1078 585 614 0 1092 979 1059 79 1077 711 479 1033 12 41 1 0 829 13 11 878 877 20 16 1062 455 977 990 1037 5 924 711 19 30 717 348 895 364 9 1 615 746 12 348 614 19 1033 692 862 0
0.38/0.47	d CHECKS 2699310
0.38/0.47	d ASSIGNMENTS 801
0.38/0.47	d NODES 801 BACKTRACKS 653 FAILURES 653 RUNTIME 0.41 TOTALTIME 0.46 NODES/s 1953.66 CHECKS/s 6.58368e+06

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2082898-1247376121/watcher-2082898-1247376121 -o /tmp/evaluation-result-2082898-1247376121/solver-2082898-1247376121 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2082898-1247376121.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): 2000 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


[startup+0 s]
/proc/loadavg: 1.91 1.98 1.99 3/74 27525
/proc/meminfo: memFree=1325920/2055924 swapFree=4192812/4192956
[pid=27525] ppid=27523 vsize=8100 CPUtime=0.19
/proc/27525/stat : 27525 (ld-linux.so.2) R 27523 27525 22627 0 -1 4194304 1287 0 0 0 19 0 0 0 19 0 1 0 24679493 8294400 1266 996147200 1448431616 1448550632 4294956208 18446744073709551615 135161293 0 0 4096 0 0 0 0 17 1 0 0
/proc/27525/statm: 2025 1266 421 29 0 840 0

[startup+0.310676 s]
/proc/loadavg: 1.91 1.98 1.99 3/74 27525
/proc/meminfo: memFree=1325920/2055924 swapFree=4192812/4192956
[pid=27525] ppid=27523 vsize=8100 CPUtime=0.29
/proc/27525/stat : 27525 (ld-linux.so.2) R 27523 27525 22627 0 -1 4194304 1287 0 0 0 29 0 0 0 20 0 1 0 24679493 8294400 1266 996147200 1448431616 1448550632 4294956208 18446744073709551615 135172204 0 0 4096 0 0 0 0 17 1 0 0
/proc/27525/statm: 2025 1266 421 29 0 840 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 8100

[startup+0.402696 s]
/proc/loadavg: 1.91 1.98 1.99 3/74 27525
/proc/meminfo: memFree=1325920/2055924 swapFree=4192812/4192956
[pid=27525] ppid=27523 vsize=8100 CPUtime=0.38
/proc/27525/stat : 27525 (ld-linux.so.2) R 27523 27525 22627 0 -1 4194304 1287 0 0 0 38 0 0 0 20 0 1 0 24679493 8294400 1266 996147200 1448431616 1448550632 4294956208 18446744073709551615 135161293 0 0 4096 0 0 0 0 17 1 0 0
/proc/27525/statm: 2025 1266 421 29 0 840 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 8100

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

Child status: 0
Real time (s): 0.485113
CPU time (s): 0.478926
CPU user time (s): 0.469928
CPU system time (s): 0.008998
CPU usage (%): 98.7246
Max. virtual memory (cumulated for all children) (KiB): 8100

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.469928
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1346
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= 25
involuntary context switches= 14

runsolver used 0.000999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node6 at 2009-07-12 07:22:01
IDJOB=2082898
IDBENCH=57651
IDSOLVER=769
FILE ID=node6/2082898-1247376121
PBS_JOBID= 9507059
Free space on /tmp= 66336 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/os-gp/normalized-gp10-01-1093.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2082898-1247376121/watcher-2082898-1247376121 -o /tmp/evaluation-result-2082898-1247376121/solver-2082898-1247376121 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2082898-1247376121.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 2960c39330e67b59bd11d1942a6cbea3
RANDOM SEED=1872936800

node6.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.263
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.263
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:      2055924 kB
MemFree:       1326400 kB
Buffers:         56224 kB
Cached:         269904 kB
SwapCached:          0 kB
Active:         531108 kB
Inactive:       120484 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1326400 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1488 kB
Writeback:           0 kB
Mapped:         336708 kB
Slab:            62660 kB
Committed_AS:   489628 kB
PageTables:       2564 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= 66332 MiB
End job on node6 at 2009-07-12 07:22:01