Trace number 1083768

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
MDG-probe 2008-06-27SAT 0.292954 0.29684

DiagnosticValue
ASSIGNMENTS248
CHECKS26775

General information on the benchmark

Namecsp/rlfapScens/
normalized-scen5.xml
MD5SUMd00375a0db2ca765457bfad019ed3136
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.292954
Satisfiable
(Un)Satisfiability was proved
Number of variables400
Number of constraints2598
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2598
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c mistral-prime version 1.313
0.00/0.00	c 
0.00/0.00	c Parsing xml file
0.00/0.00	c          domains...............     0	(4 domains)
0.00/0.00	c          variables.............     0	(400 variables)
0.00/0.01	c          predicates............     0	(2 predicates)
0.00/0.01	c          constraints...........  0.08	(2598 constraints)
0.01/0.09	c Parsing time:   0.08
0.01/0.09	c
0.01/0.09	c Building model
0.09/0.10	c         0 constants
0.09/0.10	c         0 Boolean variables    (+0)
0.09/0.10	c         0 range variables      (+0)
0.09/0.10	c         0 domain (b) variables (+0)
0.09/0.10	c       400 domain (l) variables (+0)
0.09/0.10	c      2598 constraints          (+0)
0.09/0.10	c         0 values 
0.09/0.10	c Building time:   0.01
0.09/0.10	c
0.09/0.10	c Solving instance
0.09/0.10	c          heuristic = dom/wdeg
0.09/0.10	c          Randomized probing iteration = 100
0.09/0.10	c          probing limit = 30
0.09/0.10	c          level based weights = no
0.09/0.10	c          impact probing = no
0.09/0.10	c          restart policy = No restart
0.09/0.10	c          probing .  0.18
0.19/0.28	c          Probing Nodes   248
0.19/0.28	c Solving time:   0.18
0.19/0.28	c
0.19/0.28	s SATISFIABLE
0.19/0.28	v 156 394 156 394 254 16 30 268 414 652 254 16 128 366 414 652 792 554 554 792 16 254 708 470 666 428 442 680 72 310 428 666 128 366 736 498 44 282 254 16 442 680 736 498 254 16 310 72 736 498 792 554 310 72 764 526 310 72 428 666 30 268 484 722 16 254 16 254 254 16 254 16 16 254 484 722 296 58 296 58 16 254 16 254 296 58 366 128 128 366 16 254 254 16 736 498 156 394 380 142 792 554 254 16 156 394 324 86 540 778 498 736 380 142 30 268 268 30 254 16 156 394 414 652 268 30 254 16 652 414 442 680 394 156 394 156 268 30 680 442 666 428 750 512 414 652 666 428 100 338 324 86 338 100 30 268 750 512 722 484 764 526 366 128 268 30 428 666 694 456 736 498 394 156 16 254 764 526 666 428 338 100 324 86 680 442 268 30 666 428 666 428 428 666 128 366 72 310 414 652 652 414 792 554 254 16 428 666 512 750 352 114 114 352 708 470 498 736 268 30 512 750 456 694 30 268 58 296 540 778 652 414 16 254 764 526 366 128 652 414 254 16 512 750 268 30 428 666 296 58 680 442 268 30 428 666 268 30 324 86 310 72 86 324 750 512 540 778 526 764 666 428 30 268 282 44 428 666 114 352 666 428 86 324 128 366 128 366 44 282 16 254 666 428 680 442 414 652 394 156 778 540 296 58 254 16 296 58 694 456 128 366 254 16 540 778 442 680 694 456 414 652 310 72 30 268 484 722 526 764 30 268 694 456 114 352 428 666 498 736 16 254 324 86 268 30 86 324 428 666 30 268 694 456 484 722 268 30 666 428 268 30 498 736 428 666 268 30 750 512 114 352 30 268 114 352 484 722 428 666 268 30 428 666 268 30 268 30 694 456 764 526 268 30 114 352 268 30 44 282
0.19/0.28	d CHECKS 26775
0.19/0.28	d ASSIGNMENTS 248

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-1083768-1215229352/watcher-1083768-1215229352 -o /tmp/evaluation-result-1083768-1215229352/solver-1083768-1215229352 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1083768-1215229352.xml -v 1 -rs 1305675632 -probe 1 -ph 0 -heu dom/wdeg -res no 

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.25 2.12 2.04 4/74 30309
/proc/meminfo: memFree=940600/2055920 swapFree=4176992/4192956
[pid=30309] ppid=30307 vsize=4584 CPUtime=0
/proc/30309/stat : 30309 (xsolve) R 30307 30309 27559 0 -1 4194304 347 0 0 0 0 0 0 0 18 0 1 0 645855300 4694016 313 996147200 134512640 135239859 4294956144 18446744073709551615 6956704 0 0 4096 0 0 0 0 17 0 0 0
/proc/30309/statm: 1146 322 276 177 0 49 0

[startup+0.016611 s]
/proc/loadavg: 2.25 2.12 2.04 4/74 30309
/proc/meminfo: memFree=940600/2055920 swapFree=4176992/4192956
[pid=30309] ppid=30307 vsize=4852 CPUtime=0.01
/proc/30309/stat : 30309 (xsolve) R 30307 30309 27559 0 -1 4194304 541 0 1 0 1 0 0 0 18 0 1 0 645855300 4968448 508 996147200 134512640 135239859 4294956144 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 0 0 0
/proc/30309/statm: 1213 509 397 177 0 116 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 4852

[startup+0.101621 s]
/proc/loadavg: 2.25 2.12 2.04 4/74 30309
/proc/meminfo: memFree=940600/2055920 swapFree=4176992/4192956
[pid=30309] ppid=30307 vsize=8136 CPUtime=0.09
/proc/30309/stat : 30309 (xsolve) R 30307 30309 27559 0 -1 4194304 1380 0 1 0 9 0 0 0 18 0 1 0 645855300 8331264 1347 996147200 134512640 135239859 4294956144 18446744073709551615 7222907 0 0 4096 0 0 0 0 17 0 0 0
/proc/30309/statm: 2034 1349 415 177 0 937 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8136

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

[startup+0.20163 s]
/proc/loadavg: 2.25 2.12 2.04 4/74 30309
/proc/meminfo: memFree=940600/2055920 swapFree=4176992/4192956
[pid=30309] ppid=30307 vsize=8532 CPUtime=0.19
/proc/30309/stat : 30309 (xsolve) R 30307 30309 27559 0 -1 4194304 1493 0 1 0 19 0 0 0 18 0 1 0 645855300 8736768 1460 996147200 134512640 135239859 4294956144 18446744073709551615 134535329 0 0 4096 0 0 0 0 17 0 0 0
/proc/30309/statm: 2133 1460 421 177 0 1036 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 8532

Child status: 0
Real time (s): 0.29684
CPU time (s): 0.292954
CPU user time (s): 0.282956
CPU system time (s): 0.009998
CPU usage (%): 98.6909
Max. virtual memory (cumulated for all children) (KiB): 8532

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node84 at 2008-07-05 05:42:32
IDJOB=1083768
IDBENCH=57507
IDSOLVER=342
FILE ID=node84/1083768-1215229352
PBS_JOBID= 7881787
Free space on /tmp= 66556 MiB

SOLVER NAME= MDG-probe 2008-06-27
BENCH NAME= CPAI08/csp/rlfapScens/normalized-scen5.xml
COMMAND LINE= HOME/xsolve BENCHNAME -v 1 -rs RANDOMSEED -probe 1 -ph 0 -heu dom/wdeg -res no
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1083768-1215229352/watcher-1083768-1215229352 -o /tmp/evaluation-result-1083768-1215229352/solver-1083768-1215229352 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1083768-1215229352.xml -v 1 -rs 1305675632 -probe 1 -ph 0 -heu dom/wdeg -res no

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= d00375a0db2ca765457bfad019ed3136
RANDOM SEED=1305675632

node84.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.231
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.231
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:        941080 kB
Buffers:         23588 kB
Cached:        1023084 kB
SwapCached:      10116 kB
Active:         122840 kB
Inactive:       941468 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        941080 kB
SwapTotal:     4192956 kB
SwapFree:      4176992 kB
Dirty:            1612 kB
Writeback:           0 kB
Mapped:          23768 kB
Slab:            35924 kB
Committed_AS:  1223724 kB
PageTables:       1744 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= 66556 MiB
End job on node84 at 2008-07-05 05:42:32