Trace number 231219

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.900862 0.918754

DiagnosticValue
CHECKS28756
NODES60

General information on the benchmark

Namegeom/
geo50-20-d4-75-10_ext.xml
MD5SUM675f2817bffdcc136abaa78e82fe084a
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.270958
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints459
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension459
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/231219-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.098  cpuTime=0.09  mem=6M951
0.40	   
0.40	   relations being loaded...
0.52	   
0.52	   constraints being loaded...
0.65	     nbConstraints=459  nbRelationTypes=459  nbExtensionStructures=459  nbSharedExtensionStructures=0
0.65	     nbConflictsStructures=459  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=4519  maxDegree=30
0.65	     maxArity=2
0.65	       =>  wckTime=0.351  cpuTime=0.27  mem=15M744
0.69	   
0.69	   solver IterativeSystematicSolver being built... 
0.84	       =>  wckTime=0.54  cpuTime=0.39  mem=15M213
0.85	   
0.85	   preprocessing
0.85	     nbConstraintChecks=0  nbPropagations=50  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.85	     detectedInconsistency=no
0.85	       =>  wckTime=0.0080  cpuTime=0.01  mem=15M213
0.90	   
0.90	   search
0.90	     run=0  nbConstraintChecks=28756  nbPropagations=499  nbRevisions=4404  nbUselessRevisions=3597  nbAssignments=60
0.90	     nbFailedAssignments=6  nbBacktracks=4  nbVisitedNodes=69  nbRestartNogoods=0  mapSize=3  nbInferences=0
0.90	     nbTooLargeKeys=0
0.90	       =>  wckTime=0.057  cpuTime=0.03  mem=15M213
0.90	   
0.90	   global
0.90	     nbConstraintChecks=28756  nbPropagations=549  nbRevisions=4404  nbUselessRevisions=3597  nbRestartNogoods=0
0.90	     solvingWckTime=0.059  solvingCpuTime=0.04  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.90	     globalCpuTime=0.47
0.90	       =>  wckTime=0.601  cpuTime=0.43  mem=15M213
0.90	   
0.90	s SATISFIABLE
0.90	v 6 7 12 9 13 17 11 16 6 13 2 4 15 14 19 3 8 15 15 2 18 18 12 20 15 3 14 2 19 4 18 17 2 19 3 10 10 19 15 1 7 5 7 5 4 1 7 5 13 10 
0.90	d NODES 60
0.90	d CHECKS 28756
0.90	   
0.90	   totalWckTime=0.677  totalCpuTime=0.47

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/node19/watcher-231219-1168081139 -o ROOT/results/node19/solver-231219-1168081139 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/231219-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.02 0.36 1.05 4/81 24740
/proc/meminfo: memFree=1250992/2055920 swapFree=4171232/4192956
[pid=24739] ppid=24737 vsize=1784 CPUtime=0
/proc/24739/stat : 24739 (java) D 24737 24739 24670 0 -1 0 165 0 0 0 0 0 0 0 20 0 1 0 156510404 1826816 136 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099781622 0 0 17 0 0 0
/proc/24739/statm: 446 136 102 14 0 91 0

[startup+0.104523 s]
/proc/loadavg: 0.02 0.36 1.05 4/81 24740
/proc/meminfo: memFree=1250992/2055920 swapFree=4171232/4192956
[pid=24739] ppid=24737 vsize=914988 CPUtime=0.07
/proc/24739/stat : 24739 (java) R 24737 24739 24670 0 -1 0 3017 0 1 0 6 1 0 0 24 0 8 0 156510404 936947712 2763 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4153609792 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/24739/statm: 228747 2763 1435 14 0 215242 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 914988

[startup+0.512597 s]
/proc/loadavg: 0.02 0.36 1.05 4/81 24740
/proc/meminfo: memFree=1250992/2055920 swapFree=4171232/4192956
[pid=24739] ppid=24737 vsize=915328 CPUtime=0.48
/proc/24739/stat : 24739 (java) R 24737 24739 24670 0 -1 0 6946 0 1 0 44 4 0 0 16 0 8 0 156510404 937295872 6685 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4073567214 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/24739/statm: 228832 6686 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.918754
CPU time (s): 0.900862
CPU user time (s): 0.827874
CPU system time (s): 0.072988
CPU usage (%): 98.0526
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.827874
system time used= 0.072988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9062
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= 697
involuntary context switches= 80

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

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


IDJOB= 231219
IDBENCH= 6455
FILE ID= node19/231219-1168081139

PBS_JOBID= 3476204

Free space on /tmp= 66312 MiB

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

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  675f2817bffdcc136abaa78e82fe084a

RANDOM SEED= 884039151

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.260
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.260
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:       1251344 kB
Buffers:         70568 kB
Cached:         598376 kB
SwapCached:      10036 kB
Active:         290652 kB
Inactive:       413628 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1251344 kB
SwapTotal:     4192956 kB
SwapFree:      4171232 kB
Dirty:            1960 kB
Writeback:           0 kB
Mapped:          44604 kB
Slab:            85268 kB
Committed_AS:  3619452 kB
PageTables:       2208 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= 66312 MiB



End job on node19 on Sat Jan  6 10:59:31 UTC 2007