Trace number 280549

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
AbsconMax 109 EPFCOPTIMUM 0.662898 0.729616

General information on the benchmark

NameMaxCSP/
pedigree/connell_ext.xml
MD5SUM06c4c7d489d2f5e326393eb386079261
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints14
Best CPU time to get the best result obtained on this benchmark0.008997
Satisfiable
(Un)Satisfiability was proved
Number of variables13
Number of constraints15
Maximum constraint arity3
Maximum domain size6
Number of constraints which are defined in extension15
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.30	   
0.30	Abscon 109 (November, 2006)
0.30	   
0.30	   configuration
0.30	     name=epfc.xml
0.33	   
0.33	   instance
0.33	     name=/tmp/evaluation/280549-1169306570/unknown.xml
0.36	   
0.36	   domains being loaded...
0.36	   
0.36	   variables being loaded...
0.39	     nbVariables=13  nbDomainTypes=2  minDomainSize=1  maxDomainSize=6
0.39	       =>  wckTime=0.09  cpuTime=0.07  mem=6M887
0.39	   
0.39	   relations being loaded...
0.39	   
0.39	   constraints being loaded...
0.42	     nbConstraints=15  nbRelationTypes=4  nbSingletonDomainVariables=1  nbExtensionStructures=4
0.42	     nbSharedExtensionStructures=11  nbConflictsStructures=4  nbSharedConflictsStructures=11
0.42	     nbSharedBinaryRepresentations=16  maxDegree=7  maxArity=3
0.42	       =>  wckTime=0.125  cpuTime=0.11  mem=7M879
0.46	   
0.46	   solver LocalSearchSolver being built... 
0.50	       =>  wckTime=0.203  cpuTime=0.15  mem=5M364
0.50	
0.50	s SATISFIABLE
0.50	o 3
0.50	c 12
0.51	o 5
0.51	c 10
0.51	o 6
0.51	c 9
0.51	o 7
0.51	c 8
0.51	o 8
0.51	c 7
0.51	o 9
0.51	c 6
0.51	o 10
0.51	c 5
0.51	o 12
0.51	c 3
0.51	o 13
0.51	c 2
0.51	o 14
0.51	c 1
0.51	   
0.51	   search
0.51	     run=0  nbConstraintChecks=874  nbAssignments=12
0.51	       =>  wckTime=0.012  cpuTime=0.01  mem=5M364
0.51	   
0.51	   global
0.51	     nbConstraintChecks=874  nbValidityChecks=0  nbPropagations=0  nbRevisions=0  nbUselessRevisions=0
0.51	     solvingWckTime=0.011  solvingCpuTime=0.0  expiredTime=no  totalExploration=no  nbFoundSolutions=0
0.51	     globalCpuTime=0.2
0.51	       =>  wckTime=0.214  cpuTime=0.15  mem=5M364
0.51	   
0.51	   solver IterativeSystematicSolver being built... 
0.64	       =>  wckTime=0.344  cpuTime=0.26  mem=16M402
0.67	   
0.67	   preprocessing
0.67	     nbConstraintChecks=510  nbValidityChecks=1133  nbPropagations=0  nbRevisions=0  nbUselessRevisions=0
0.67	     nbRemovedValues=52  detectedInconsistency=yes
0.67	       =>  wckTime=0.021  cpuTime=0.01  mem=16M402
0.67	   
0.67	   global
0.67	     nbConstraintChecks=510  nbValidityChecks=1133  nbRestartNogoods=0  solvingWckTime=0.024  solvingCpuTime=0.01
0.67	     expiredTime=no  totalExploration=yes  nbFoundSolutions=0  globalCpuTime=0.32
0.67	       =>  wckTime=0.369  cpuTime=0.27  mem=16M402
0.67	
0.67	s OPTIMUM FOUND
0.67	v 3 4 3 4 4 3 3 4 3 3 1 4 -1 
0.67	   
0.67	   totalWckTime=0.445  totalCpuTime=0.32

Verifier Data (download as text)

1 unsatisfied constraints, 14 satisfied constraints

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node61/watcher-280549-1169306570 -o ROOT/results/node61/solver-280549-1169306570 -C 2400 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar epfc.xml 1 XSax /tmp/evaluation/280549-1169306570/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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: 0.86 0.97 0.99 4/74 4723
/proc/meminfo: memFree=1311816/2055920 swapFree=4191892/4192956
[pid=4722] ppid=4720 vsize=18540 CPUtime=0
/proc/4722/stat : 4722 (runsolver) R 4720 4722 4383 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 279054882 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 246406507815 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/4722/statm: 4635 279 244 17 0 2626 0

[startup+0.107971 s]
/proc/loadavg: 0.86 0.97 0.99 4/74 4723
/proc/meminfo: memFree=1311816/2055920 swapFree=4191892/4192956
[pid=4722] ppid=4720 vsize=914988 CPUtime=0.08
/proc/4722/stat : 4722 (java) R 4720 4722 4383 0 -1 0 3046 0 1 0 7 1 0 0 20 0 8 0 279054882 936947712 2792 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4155477106 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/4722/statm: 228747 2792 1445 14 0 215242 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 914988

[startup+0.516032 s]
/proc/loadavg: 0.86 0.97 0.99 4/74 4723
/proc/meminfo: memFree=1311816/2055920 swapFree=4191892/4192956
[pid=4722] ppid=4720 vsize=915336 CPUtime=0.49
/proc/4722/stat : 4722 (java) R 4720 4722 4383 0 -1 0 6824 0 1 0 44 5 0 0 22 0 8 0 279054882 937304064 6562 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/4722/statm: 228833 6562 2478 14 0 215303 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915336

Child status: 0
Real time (s): 0.729616
CPU time (s): 0.662898
CPU user time (s): 0.594909
CPU system time (s): 0.067989
CPU usage (%): 90.8557
Max. virtual memory (cumulated for all children) (KiB): 915980

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.594909
system time used= 0.067989
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8965
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= 565
involuntary context switches= 663

runsolver used 0.003999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node61 on Sat Jan 20 15:22:50 UTC 2007


IDJOB= 280549
IDBENCH= 11872
IDSOLVER= 68
FILE ID= node61/280549-1169306570

PBS_JOBID= 3610167

Free space on /tmp= 66559 MiB

SOLVER NAME= AbsconMax 109 EPFC
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/pedigree/connell_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar epfc.xml 1 XSax /tmp/evaluation/280549-1169306570/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node61/watcher-280549-1169306570 -o ROOT/results/node61/solver-280549-1169306570 -C 2400 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar epfc.xml 1 XSax /tmp/evaluation/280549-1169306570/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  06c4c7d489d2f5e326393eb386079261

RANDOM SEED= 938303361

TIME LIMIT= 2400 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.259
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.259
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:       1312872 kB
Buffers:         54832 kB
Cached:         586064 kB
SwapCached:        480 kB
Active:         115912 kB
Inactive:       546536 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1312872 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            6324 kB
Writeback:           0 kB
Mapped:          31264 kB
Slab:            66220 kB
Committed_AS:  5466520 kB
PageTables:       1748 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= 66559 MiB



End job on node61 on Sat Jan 20 15:22:51 UTC 2007