Trace number 230819

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.871866 0.950851

DiagnosticValue
CHECKS73700
NODES51

General information on the benchmark

Namegeom/
geo50-20-d4-75-59_ext.xml
MD5SUM73b202a19cfb2790300458596f366637
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.12498
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints386
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension386
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.33	   
0.33	Abscon 109 (November, 2006)
0.33	   
0.33	   configuration
0.33	     name=esac.xml
0.36	   
0.36	   instance
0.36	     name=/tmp/evaluation/230819-1168317192/unknown.xml
0.39	   
0.39	   domains being loaded...
0.40	   
0.40	   variables being loaded...
0.43	     nbVariables=50  nbDomainTypes=1  minDomainSize=20  maxDomainSize=20
0.43	       =>  wckTime=0.1  cpuTime=0.08  mem=6M951
0.43	   
0.43	   relations being loaded...
0.55	   
0.55	   constraints being loaded...
0.65	     nbConstraints=386  nbRelationTypes=386  nbExtensionStructures=386  nbSharedExtensionStructures=0
0.65	     nbConflictsStructures=386  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=3401  maxDegree=24
0.65	     maxArity=2
0.65	       =>  wckTime=0.322  cpuTime=0.24  mem=13M860
0.70	   
0.70	   solver IterativeSystematicSolver being built... 
0.84	       =>  wckTime=0.513  cpuTime=0.35  mem=15M233
0.89	   
0.89	   preprocessing
0.89	     nbConstraintChecks=56097  nbPropagations=954  nbRevisions=5998  nbUselessRevisions=4899  nbSingletonTests=64
0.89	     nbEffectiveSingletonTests=0  nbESACBranches=6  nbRemovedValues=0  detectedInconsistency=no
0.89	       =>  wckTime=0.048  cpuTime=0.02  mem=15M233
0.92	   
0.92	   search
0.92	     run=0  nbConstraintChecks=17603  nbPropagations=1296  nbRevisions=8016  nbUselessRevisions=6556  nbAssignments=51
0.92	     nbFailedAssignments=1  nbBacktracks=0  nbVisitedNodes=53  nbRestartNogoods=0  mapSize=0  nbInferences=0
0.92	     nbTooLargeKeys=0
0.92	       =>  wckTime=0.069  cpuTime=0.04  mem=15M233
0.92	   
0.92	   global
0.92	     nbConstraintChecks=73700  nbPropagations=2250  nbRevisions=14014  nbUselessRevisions=11455  nbRestartNogoods=0
0.92	     solvingWckTime=0.07  solvingCpuTime=0.04  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.92	     globalCpuTime=0.45
0.92	       =>  wckTime=0.585  cpuTime=0.4  mem=15M233
0.92	   
0.92	s SATISFIABLE
0.92	v 10 19 3 4 17 8 1 18 15 9 7 9 12 8 5 1 12 10 17 18 4 11 17 7 8 1 4 8 18 3 14 20 5 20 17 11 19 10 4 11 3 17 1 3 15 1 18 20 14 18 
0.92	d NODES 51
0.92	d CHECKS 73700
0.92	   
0.92	   totalWckTime=0.659  totalCpuTime=0.46

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/node43/watcher-230819-1168317192 -o ROOT/results/node43/solver-230819-1168317192 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230819-1168317192/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.54 1.10 1.53 3/65 15348
/proc/meminfo: memFree=1461032/2055920 swapFree=4192812/4192956
[pid=15347] ppid=15345 vsize=172 CPUtime=0
/proc/15347/stat : 15347 (java) R 15345 15347 11957 0 -1 0 217 0 0 0 0 0 0 0 19 0 1 0 180118736 176128 24 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4731179 0 0 4096 0 0 0 0 17 1 0 0
/proc/15347/statm: 43 24 18 14 0 3 0

[startup+0.106833 s]
/proc/loadavg: 0.54 1.10 1.53 3/65 15348
/proc/meminfo: memFree=1461032/2055920 swapFree=4192812/4192956
[pid=15347] ppid=15345 vsize=907808 CPUtime=0.06
/proc/15347/stat : 15347 (java) R 15345 15347 11957 0 -1 0 2516 0 1 0 5 1 0 0 20 0 4 0 180118736 929595392 2263 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23755 18446744073709551615 0 0 17 0 0 0
/proc/15347/statm: 226952 2263 1236 14 0 214535 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 907808

[startup+0.514892 s]
/proc/loadavg: 0.54 1.10 1.53 3/65 15348
/proc/meminfo: memFree=1461032/2055920 swapFree=4192812/4192956
[pid=15347] ppid=15345 vsize=915328 CPUtime=0.46
/proc/15347/stat : 15347 (java) R 15345 15347 11957 0 -1 0 6725 0 1 0 41 5 0 0 17 0 8 0 180118736 937295872 6464 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4073567214 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/15347/statm: 228832 6464 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.46
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.950851
CPU time (s): 0.871866
CPU user time (s): 0.792879
CPU system time (s): 0.078987
CPU usage (%): 91.6932
Max. virtual memory (cumulated for all children) (KiB): 915456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.792879
system time used= 0.078987
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8797
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= 671
involuntary context switches= 110

runsolver used 0.001999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node43 on Tue Jan  9 04:33:16 UTC 2007


IDJOB= 230819
IDBENCH= 6434
FILE ID= node43/230819-1168317192

PBS_JOBID= 3502524

Free space on /tmp= 66499 MiB

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

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  73b202a19cfb2790300458596f366637

RANDOM SEED= 292239048

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.278
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.278
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:       1461512 kB
Buffers:         68856 kB
Cached:         454200 kB
SwapCached:          0 kB
Active:         241268 kB
Inactive:       297120 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1461512 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2040 kB
Writeback:           0 kB
Mapped:          25480 kB
Slab:            42104 kB
Committed_AS:  4050504 kB
PageTables:       1392 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= 66499 MiB



End job on node43 on Tue Jan  9 04:33:19 UTC 2007