Trace number 231238

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 ACSAT 0.866867 0.92234

DiagnosticValue
CHECKS25872
NODES60

General information on the benchmark

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

Solver Data (download as text)

0.30	   
0.30	Abscon 109 (November, 2006)
0.30	   
0.30	   configuration
0.30	     name=mac.xml
0.33	   
0.33	   instance
0.33	     name=/tmp/evaluation/231238-1168081139/unknown.xml
0.36	   
0.36	   domains being loaded...
0.36	   
0.36	   variables being loaded...
0.40	     nbVariables=50  nbDomainTypes=1  minDomainSize=20  maxDomainSize=20
0.40	       =>  wckTime=0.097  cpuTime=0.08  mem=6M951
0.40	   
0.40	   relations being loaded...
0.51	   
0.51	   constraints being loaded...
0.62	     nbConstraints=373  nbRelationTypes=373  nbExtensionStructures=373  nbSharedExtensionStructures=0
0.62	     nbConflictsStructures=373  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=3311  maxDegree=23
0.62	     maxArity=2
0.62	       =>  wckTime=0.317  cpuTime=0.24  mem=13M780
0.66	   
0.66	   solver IterativeSystematicSolver being built... 
0.81	       =>  wckTime=0.505  cpuTime=0.36  mem=14M988
0.81	   
0.81	   preprocessing
0.81	     nbConstraintChecks=0  nbPropagations=50  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.81	     detectedInconsistency=no
0.81	       =>  wckTime=0.0050  cpuTime=0.0  mem=14M988
0.87	   
0.87	   search
0.87	     run=0  nbConstraintChecks=25872  nbPropagations=479  nbRevisions=3566  nbUselessRevisions=2782  nbAssignments=60
0.87	     nbFailedAssignments=4  nbBacktracks=6  nbVisitedNodes=69  nbRestartNogoods=0  mapSize=4  nbInferences=0
0.87	     nbTooLargeKeys=0
0.87	       =>  wckTime=0.059  cpuTime=0.03  mem=14M988
0.87	   
0.87	   global
0.87	     nbConstraintChecks=25872  nbPropagations=529  nbRevisions=3566  nbUselessRevisions=2782  nbRestartNogoods=0
0.87	     solvingWckTime=0.061  solvingCpuTime=0.03  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.87	     globalCpuTime=0.45
0.87	       =>  wckTime=0.568  cpuTime=0.4  mem=14M988
0.87	   
0.87	s SATISFIABLE
0.87	v 19 16 17 5 8 13 10 18 13 15 5 15 10 2 5 8 8 17 18 19 2 6 8 19 13 13 8 14 7 14 15 17 16 1 3 8 5 16 7 16 18 5 5 11 1 17 18 14 12 2 
0.87	d NODES 60
0.87	d CHECKS 25872
0.87	   
0.87	   totalWckTime=0.644  totalCpuTime=0.45

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/node39/watcher-231238-1168081139 -o ROOT/results/node39/solver-231238-1168081139 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/231238-1168081139/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.03 0.26 0.83 4/68 22018
/proc/meminfo: memFree=1731792/2055920 swapFree=4192812/4192956
[pid=22017] ppid=22015 vsize=1784 CPUtime=0
/proc/22017/stat : 22017 (java) D 22015 22017 21950 0 -1 0 169 0 0 0 0 0 0 0 19 0 1 0 156515366 1826816 140 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/22017/statm: 446 140 106 14 0 91 0

[startup+0.10646 s]
/proc/loadavg: 0.03 0.26 0.83 4/68 22018
/proc/meminfo: memFree=1731792/2055920 swapFree=4192812/4192956
[pid=22017] ppid=22015 vsize=914988 CPUtime=0.09
/proc/22017/stat : 22017 (java) R 22015 22017 21950 0 -1 0 3069 0 1 0 7 2 0 0 16 0 8 0 156515366 936947712 2815 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4155170016 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/22017/statm: 228747 2815 1452 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.518498 s]
/proc/loadavg: 0.03 0.26 0.83 4/68 22018
/proc/meminfo: memFree=1731792/2055920 swapFree=4192812/4192956
[pid=22017] ppid=22015 vsize=915328 CPUtime=0.49
/proc/22017/stat : 22017 (java) R 22015 22017 21950 0 -1 0 7007 0 1 0 44 5 0 0 16 0 8 0 156515366 937295872 6746 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4072926671 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/22017/statm: 228832 6746 2138 14 0 215302 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.92234
CPU time (s): 0.866867
CPU user time (s): 0.78788
CPU system time (s): 0.078987
CPU usage (%): 93.9856
Max. virtual memory (cumulated for all children) (KiB): 915456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.78788
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= 8686
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= 638
involuntary context switches= 101

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node39 on Sat Jan  6 10:59:04 UTC 2007


IDJOB= 231238
IDBENCH= 6456
FILE ID= node39/231238-1168081139

PBS_JOBID= 3476205

Free space on /tmp= 66530 MiB

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

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  fcc723702dbd9f7d725a34a5013e12ba

RANDOM SEED= 916887949

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.236
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.236
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:       1732200 kB
Buffers:         27808 kB
Cached:         205092 kB
SwapCached:          0 kB
Active:          76544 kB
Inactive:       176512 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1732200 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2528 kB
Writeback:           0 kB
Mapped:          30272 kB
Slab:            56376 kB
Committed_AS:  3021896 kB
PageTables:       1620 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= 66531 MiB



End job on node39 on Sat Jan  6 10:59:32 UTC 2007