Trace number 230952

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
Abscon 109 ESACSAT 0.831873 0.867253

DiagnosticValue
CHECKS18398
NODES0

General information on the benchmark

Namegeom/
geo50-20-d4-75-24_ext.xml
MD5SUM7c4e8f924c770ec00d720e1f8e8a4ad3
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.12698
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints393
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension393
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.29	   
0.29	Abscon 109 (November, 2006)
0.29	   
0.29	   configuration
0.29	     name=esac.xml
0.32	   
0.32	   instance
0.32	     name=/tmp/evaluation/230952-1168317365/unknown.xml
0.35	   
0.35	   domains being loaded...
0.35	   
0.35	   variables being loaded...
0.39	     nbVariables=50  nbDomainTypes=1  minDomainSize=20  maxDomainSize=20
0.39	       =>  wckTime=0.095  cpuTime=0.08  mem=6M951
0.39	   
0.39	   relations being loaded...
0.50	   
0.50	   constraints being loaded...
0.60	     nbConstraints=393  nbRelationTypes=393  nbExtensionStructures=393  nbSharedExtensionStructures=0
0.60	     nbConflictsStructures=393  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=3430  maxDegree=22
0.60	     maxArity=2
0.60	       =>  wckTime=0.312  cpuTime=0.25  mem=13M925
0.64	   
0.64	   solver IterativeSystematicSolver being built... 
0.79	       =>  wckTime=0.498  cpuTime=0.37  mem=15M314
0.82	   
0.82	   preprocessing
0.82	     nbConstraintChecks=18398  nbPropagations=372  nbRevisions=2215  nbUselessRevisions=1858  nbSingletonTests=50
0.82	     nbEffectiveSingletonTests=0  nbESACBranches=1  nbRemovedValues=0  detectedInconsistency=no
0.82	       =>  wckTime=0.03  cpuTime=0.02  mem=15M314
0.82	   
0.82	   global
0.82	     nbConstraintChecks=18398  nbPropagations=372  nbRevisions=2215  nbUselessRevisions=1858  nbRestartNogoods=0
0.82	     solvingWckTime=0.031  solvingCpuTime=0.02  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.82	     globalCpuTime=0.43
0.82	       =>  wckTime=0.532  cpuTime=0.39  mem=15M314
0.83	   
0.83	s SATISFIABLE
0.83	v 1 2 16 4 6 17 1 2 5 10 4 5 5 16 2 1 2 9 7 2 17 4 12 6 1 13 7 14 2 17 18 9 1 19 4 10 9 16 13 6 3 3 7 7 4 3 3 1 17 7 
0.83	d NODES 0
0.83	d CHECKS 18398
0.83	   
0.83	   totalWckTime=0.604  totalCpuTime=0.44

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/node76/watcher-230952-1168317365 -o ROOT/results/node76/solver-230952-1168317365 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230952-1168317365/unknown.xml 

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: 0.30 0.86 1.39 3/70 20164
/proc/meminfo: memFree=1496280/2055888 swapFree=4095388/4096564
[pid=20163] ppid=20161 vsize=1788 CPUtime=0
/proc/20163/stat : 20163 (java) R 20161 20163 19363 0 -1 0 133 0 0 0 0 0 0 0 20 0 1 0 180134159 1830912 103 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 134542080 0 0 4096 0 0 0 0 17 1 0 0
/proc/20163/statm: 447 108 85 14 0 91 0

[startup+0.103199 s]
/proc/loadavg: 0.30 0.86 1.39 3/70 20164
/proc/meminfo: memFree=1496280/2055888 swapFree=4095388/4096564
[pid=20163] ppid=20161 vsize=914992 CPUtime=0.08
/proc/20163/stat : 20163 (java) S 20161 20163 19363 0 -1 0 2996 0 1 0 7 1 0 0 22 0 8 0 180134159 936951808 2744 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/20163/statm: 228748 2744 1428 14 0 215242 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 914992

[startup+0.511273 s]
/proc/loadavg: 0.30 0.86 1.39 3/70 20164
/proc/meminfo: memFree=1496280/2055888 swapFree=4095388/4096564
[pid=20163] ppid=20161 vsize=915332 CPUtime=0.49
/proc/20163/stat : 20163 (java) R 20161 20163 19363 0 -1 0 7081 0 1 0 46 3 0 0 16 0 8 0 180134159 937299968 6822 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4152815842 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/20163/statm: 228833 6822 2139 14 0 215302 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915332

Child status: 0
Real time (s): 0.867253
CPU time (s): 0.831873
CPU user time (s): 0.773882
CPU system time (s): 0.057991
CPU usage (%): 95.9204
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.773882
system time used= 0.057991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8789
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= 631
involuntary context switches= 93

runsolver used 0.003999 s user time and 0.002999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Tue Jan  9 04:36:08 UTC 2007


IDJOB= 230952
IDBENCH= 6441
FILE ID= node76/230952-1168317365

PBS_JOBID= 3502792

Free space on /tmp= 66647 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-24_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230952-1168317365/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-230952-1168317365 -o ROOT/results/node76/solver-230952-1168317365 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230952-1168317365/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  7c4e8f924c770ec00d720e1f8e8a4ad3

RANDOM SEED= 778556025

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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1496696 kB
Buffers:         77440 kB
Cached:         396228 kB
SwapCached:        428 kB
Active:         163828 kB
Inactive:       324896 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1496696 kB
SwapTotal:     4096564 kB
SwapFree:      4095388 kB
Dirty:            1932 kB
Writeback:           0 kB
Mapped:          24144 kB
Slab:            56776 kB
Committed_AS:  6722340 kB
PageTables:       1424 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66647 MiB



End job on node76 on Tue Jan  9 04:36:13 UTC 2007