Geodatabase Performance Factors and Tools - Amazon S3 · Geodatabase Performance Factors and Tools. ... ch er se Voltag e Re g Delivery P u l or H o t re e t ar y G ... Event monitor

1Enterprise ArcGIS Performance and ScalabilityESRI Worldwide Business Partner Conference 2005

Geodatabase Performance Factors and Tools

Enterprise ArcGIS Performance and ScalabilityESRI International User Conference 2005 2

Agenda

Performance Investigation

Tools Oracle Trace

Geodatabase Toolset (GDBT)When to use and Why for each command


Conceptual View


ArcGIS overview

ArcGIS Desktop

ArcGIS Server

ArcIMS ArcGIS Mobile ArcPad

ArcGIS Engine

Desktop GIS Embedded GIS Server GIS Mobile GIS

GeodatabaseDBMSFile-based XML

ArcSDE

ArcEditor

ArcView

ArcInfo

Engine Developer Kit

Server Developer Kit

CustomizationDesktop Developer Kit

.NET C++ VB Java.NET C++ VB .NETADF

JavaADF C++

ArcObjects

CustomizationXML+ VBScriptArcPad Application

Builder

JavaScriptHTML/DHTML

XML.NET

ServicesJSPJava

ActiveX (ASP)ColdFusion


Performance Investigation Roadmap

Performance Problem

Client Problem Server Problem

•Draw

•Edit

•Reconcile


Performance Investigation


Versioning performance factors

Performance can degrade over timeWorkflow often generates un-needed versions

Versions may just “sit” out there preventing the state tree from being compressed

What contributes mostly to the versioning performance?Size of the state_lineages table?

Size of the delta tables?

Number of versions?

Number of edits for a version (lineage)?

Answer: Number of edits for a version (lineage)


Number of EditsWill my versioned geodatabase scale indefinitely?

Edit Operation Response Time

27

22 2321

1012

1

2323 22

17

108

10

1

8

21

99

24

9 9

1919

0

5

10

15

20

25

30

Primary

Con

ducto

r -OH

Reclos

erSwitc

hSec

tionli

zer

Fuse

Capac

itor

Voltag

e Reg

ulator

Dist. D

elive

ry Poin

t

Transfo

rmer

- OHStre

etligh

t

Primary

Con

ducto

r -UG

Step Tran

sform

er

1.3M Changes 0 Changes


Number of editsResponse time increases with a number of edits in the version lineage (not total delta size)

More edits => higher Logical I/O

Normal filter query performance - Oracle

02468

10121416

V0his

t_100

khis

t_200

khis

t_300

khis

t_400

khis

t_500

khis

t_600

khis

t_700

khis

t_800

khis

t_900

khis

t_100

0k

edits

elap

sed

(sec

)


select V__324.*

from

(SELECT b.OID,b.PAGENUMBER,b.PAGEBLOB /* ArcSDE NORMAL_FILTER */ FROM

DOMINION.N_6_E0 b WHERE (b.OID,b.OID /* Oracle 815 bug work around.*/) NOT

IN (SELECT /*+ HASH_AJ INDEX(D324 D324_PK) */ SDE_DELETES_ROW_ID,

SDE_DELETES_ROW_ID FROM DOMINION.D324 WHERE DELETED_AT IN (SELECT /*+

USE_HASH (l) INDEX(l LINEAGES_PK) */ l.lineage_id FROM SDE.state_lineages l

WHERE l.lineage_name = :lineage_name AND l.lineage_id <= :state_id1)) UNION

ALL SELECT a.OID,a.PAGENUMBER,a.PAGEBLOB FROM DOMINION.A324 a,

SDE.state_lineages SL WHERE (a.OID,a.SDE_STATE_ID) NOT IN (SELECT /*+

HASH_AJ INDEX(D324 D324_PK) */ SDE_DELETES_ROW_ID,SDE_STATE_ID FROM

DOMINION.D324 WHERE DELETED_AT IN (SELECT /*+ USE_HASH (l) INDEX(l

LINEAGES_PK) */ l.lineage_id FROM SDE.state_lineages l WHERE l.lineage_name

= :lineage_name AND l.lineage_id <= :state_id1)) AND a.SDE_STATE_ID =

SL.lineage_id AND SL.lineage_name = :lineage_name AND SL.lineage_id <=

:state_id1 ) V__324 where (PageNumber = :"SYS_B_0")

call count cpu elapsed disk query current rows

------- ------ -------- ---------- ---------- ---------- ---------- ----------

Parse 33 0.00 0.00 0 0 0 0

Execute 33 0.01 0.02 0 0 0 0

Fetch 33 0.09 0.08 0 3127 0 33

------- ------ -------- ---------- ---------- ---------- ---------- ----------

total 99 0.10 0.12 0 3127 0 33

Compress - well compressed geodatabase


select V__324.*

from

(SELECT b.OID,b.PAGENUMBER,b.PAGEBLOB /* ArcSDE NORMAL_FILTER */ FROM

DOMINION.N_6_E0 b WHERE (b.OID,b.OID /* Oracle 815 bug work around.*/) NOT

IN (SELECT /*+ HASH_AJ INDEX(D324 D324_PK) */ SDE_DELETES_ROW_ID,

SDE_DELETES_ROW_ID FROM DOMINION.D324 WHERE DELETED_AT IN (SELECT /*+

USE_HASH (l) INDEX(l LINEAGES_PK) */ l.lineage_id FROM SDE.state_lineages l

WHERE l.lineage_name = :lineage_name AND l.lineage_id <= :state_id1)) UNION

ALL SELECT a.OID,a.PAGENUMBER,a.PAGEBLOB FROM DOMINION.A324 a,

SDE.state_lineages SL WHERE (a.OID,a.SDE_STATE_ID) NOT IN (SELECT /*+

HASH_AJ INDEX(D324 D324_PK) */ SDE_DELETES_ROW_ID,SDE_STATE_ID FROM

DOMINION.D324 WHERE DELETED_AT IN (SELECT /*+ USE_HASH (l) INDEX(l

LINEAGES_PK) */ l.lineage_id FROM SDE.state_lineages l WHERE l.lineage_name

= :lineage_name AND l.lineage_id <= :state_id1)) AND a.SDE_STATE_ID =

SL.lineage_id AND SL.lineage_name = :lineage_name AND SL.lineage_id <=

:state_id1 ) V__324 where (PageNumber = :"SYS_B_0")

call count cpu elapsed disk query current rows

------- ------ -------- ---------- ---------- ---------- ---------- ----------

Parse 59 0.09 0.07 0 0 0 0

Execute 59 0.10 0.07 0 0 0 0

Fetch 59 4.98 4.88 0 111947 0 59

------- ------ -------- ---------- ---------- ---------- ---------- ----------

total 177 5.17 5.03 0 111947 0 59

Compress – not compressed geodatabase


DominionThousands of versions

Compress every <time>

Each editor has own versionEdit version reconciled to DEFAULT daily

Design versionActive for project duration

Reconciled to DEFAULT after project complete

Versioning Workflow: Case Study


DBMS Session Tracing


DBMS tracing - events

The databases instrument various activitiesSQL statements

I/O requests

Memory usage (hit ratios and sorting)

Wait events

Allow both instance and session traces

Instance trace usually has too much information

Session trace gives exactly what the application did while running the test


Enabling DBMS trace

OracleEvent 10046, levels 8, 12

DB2Event monitor

InformixSet explain, onstat –g sql

SqlServerSQL Profiler

sp_trace_create(), sp_trace_setstatus()


Enabling DBMS trace: PTS


Enabling Oracle Tracing If Not pGxObj Is Nothing And pGxObj.Parent.Category = "Spatial Database Connection" Then

Dim pWorksp As IWorkspaceSet pGXDB = pGxObj.ParentSet pWorksp = pGXDB.WorkspacesName = "trc1"pWorksp.ExecuteSQL "alter session set tracefile_identifier = '" & sName & "'"pWorksp.ExecuteSQL "alter session set events '10046 trace name context forever, level 12'"Set pName = pGxObj.InternalObjectNameSet pTable = pName.OpenpWorksp.ExecuteSQL "alter session set events '10046 trace name context off'"

----------------------------------------------------------------------------------------------------------------Dim pC As ICursorDim pRow As IRowsName = "trc2"pWorksp.ExecuteSQL "alter session set tracefile_identifier = '" & sName & "'"pWorksp.ExecuteSQL "alter session set events '10046 trace name context forever, level 12'"Set pC = pTable.Search(Nothing, True)Set pRow = pC.NextRowpWorksp.ExecuteSQL "alter session set events '10046 trace name context off'"


Raw Oracle trace file

PARSING IN CURSOR #10 len=85 dep=0 uid=535 oct=3 lid=535 tim=219903476 hv=290318596 ad='e2707428‘

SELECT state_id,owner,creation_time,closing_time FROM SDE.statesWHERE state_id = :id

PARSE #10:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=0,tim=219903476EXEC #10:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=219903476FETCH #10:c=0,e=0,p=0,cr=3,cu=0,mis=0,r=1,dep=0,og=4,tim=219903476STAT #10 id=1 cnt=1 pid=0 pos=0 obj=4497 op='TABLE ACCESS BY INDEX

ROWID STATES 'STAT #10 id=2 cnt=2 pid=1 pos=1 obj=4498 op='INDEX UNIQUE SCAN ‘WAIT #10: nam='db file scattered read' ela= 3 p1=9 p2=39429 p3=1WAIT #10: nam='latch free' ela= 2 p1=-316822468 p2=105 p3=0


Oracle Session Tracing: TKPROF

ParseValidate statement syntaxVerify privileges and existence of referenced objectsGenerate execution plan

ExecuteOracle server process finds data

FetchOracle server process returns data to client

call count cpu elapsed disk query current rows------- ------ -------- ---------- ---------- ---------- ---------- ----------Parse 1 0.00 0.00 0 0 0 0Execute 1 0.00 0.00 0 0 0 0Fetch 325 0.47 0.56 60 33256 0 32426------- ------ -------- ---------- ---------- ---------- ---------- ----------total 327 0.47 0.56 60 33256 0 32426

Number of times call was made

Number of rows fetched


DBMS tracing – wait events

9i tkprof now shows us the wait events for each query…


SQL Server TracingEnabling Tracing

Enterprise Manager > Tools > SQL ProfilerNew > Trace

ScriptGenerate from SQL Profiler

Codesp_trace_create

sp_trace_setevent


DBMS Instance Snapshots and Reports


DBMS Instance Reports: Oracle StatsPack

Collects instance statistics“instance health and load” summary page

Instance Efficiency Percentages

High-resource SQL statements

Top 5 Timed Events

Statistics stored in table

Very useful for instance monitoring

Use dbms_job to automate statistics collectionRun every hour

dbms_job.submit(:jobno, 'statspack.snap;', trunc(sysdate+1/24,'HH'),'trunc(SYSDATE+1/24,''HH'')', TRUE, :instno);





Single connection Information and statistics is not collected

Not useful for:Diagnosis of application performance

Diagnosis of application generated RDBMS errors

Use Oracle trace


Operating System Monitoring Tools


Operating System statisticsPerfmon

Use Perfmon to capture client and server performance statistics including:

CPU utilizationMemory utilizationNetwork utilizationDisk utilization

Perfmon offers several other performance objects for more detailed analysisPerfmon statistics can be used to:

Analyze system performance and assist with pin-pointing bottlenecksDetermine relative client/server performance loads to estimate scalability


Operating System statistics

PerfmonExample 1: Perfmon can be used to determine a process memory leak over time. For this example, a Perfmon log was captured and then loaded into Excel for analysis.

Process Working Set

10000000

10100000

10200000

10300000

10400000

10500000

10600000

10700000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49

Sample

Wor

king

Set

(Byt

es)

Process Working Set


Operating System statistics

PerfmonExample 2: Perfmon can be used to determine relative client/server loads for scalability analysis . Again, Excel wasutilized to perform the analysis.


Operating System statistics: vmstatFri May 16 20:46:57 JST 2003

vms_topaz

procs memory swap io system cpu

r b w swpd free buff cache si so bi bo in cs us sy id

1 0 0 0 5096 388416 4588720 0 0 1 3 4 3 0 0 0

0 0 0 0 5100 388424 4588704 0 0 0 80 114 97 0 1 99

0 0 0 0 6752 388424 4587028 0 0 0 72 119 88 1 1 98

0 0 0 0 6744 388432 4587028 0 0 0 218 127 95 0 1 99

0 0 0 0 6688 388432 4587028 0 0 0 50 264 832 2 1 97

0 0 0 0 6676 388432 4587032 0 0 0 28 176 311 1 1 98

0 0 0 0 6668 388440 4587032 0 0 0 60 139 196 1 0 98

0 0 0 0 6668 388440 4587032 0 0 0 0 124 150 0 1 99

1 0 0 0 6576 388448 4587032 0 0 0 148 588 1907 9 2 89

0 0 0 0 6180 388448 4587080 0 0 24 202 593 2301 12 2 86

0 0 0 0 5996 388448 4587148 0 0 32 260 717 2838 16 2 82

0 0 0 0 5880 388472 4587148 0 0 0 220 652 2690 10 1 89

2 0 0 0 5320 388472 4587148 0 0 0 326 850 3614 30 5 65

1 0 0 0 5104 388500 4587072 0 0 8 482 1031 3965 34 5 61

5 0 1 0 5096 388500 4586612 0 0 24 702 885 3967 38 5 56

5 0 0 0 5092 388516 4585940 0 0 16 844 1078 4838 49 7 44

5 0 0 0 5092 388516 4585580 0 0 44 850 1292 5648 65 11 24

9 0 0 0 5096 388516 4585088 0 0 0 978 1244 5684 71 9 20

6 0 0 0 5096 388540 4584804 0 0 32 994 1191 5503 71 10 19

5 0 1 0 5092 388540 4584676 0 0 8 894 1127 4895 77 9 14

8 0 0 0 5156 388560 4584380 0 0 12 946 1148 4993 78 9 13


DBMS server

Database Instance activityMemory

CPU

Throughput

Network

StorageSAN

VLDB, Partitioning


Server/instance activity






How to tune the DBMS?

ArcSDE Configuration and Tuning guide

Baseline tuning parameters

The initial tuning for ArcSDE application

For all supported platforms

Release depenpenccy

Follows the ArcGIS release schedule

New DBMS releases


DBMS maintenance work

Space management

DBMS statistics

Auto-statistics?

Scheduled update of dbms statistics

Lock statistics

Optimizer “tuning”

Observing slow running sql

Identifying and fixing/improving “wait events”


Space management

Most larger databases use some sort of SAN

RAIDs and LUNsForget about spending too much time on tuning I/O at the device level.

Consider where you put the data (partitions)

VLDB will be I/O bound and require much more planning (e.g. separate spatial indexes from base tables, consider partitioningdbms tables and indexes)


ArcSDE


ArcSDE configuration and tuning

The server config parametersGiomgr.def in 8.x

In the DBMS for 9.x

ConfigurationsApplication server

Direct connect

Remote application sever (1..m)

Single- and multi-database configurations


Server_Config/sdeconfig

Server parameters in server_config tableEarlier versions used giomgr.defs file

Parameters can be changed without recycling the application server:

C:\sdeconfig -o alter -v MAXBLOBSIZE=2000000 -u sde -p sde -s esldb2

ArcSDE 9.2 Oracle8i Build 2056 Wed Jan 26 13:47:33 PST 2005Attribute Administration Utility-----------------------------------------------------Alter SERVER_CONFIG Table. Are you sure? (Y/N): y

Successfully altered SERVER_CONFIG Table.


Server Parameters

Data transmissionMINBUFSIZE 16384

MAXBUFSIZE 65536

MINBUFOBJECTS 512

SHAPEPTSBUFSIZE 400000

ATTRBUFSIZE 50000

RASTERBUFSIZE 102400

MAXARRAYSIZE 100

MAXARRAYBYTES 550000

LogfilesMAXSTANDALONELOGS 0ALLOWSESSIONLOGFILE FALSELOGFILEPOOLSIZE 0HOLDLOGPOOLTABLES TRUE

Used to set the type of logfiles.

The default parameters should be applied unless there is a specific need to change them. Increasing/decreasing buffer sizes usually doesn’t lead to improved performance.


Server Parameters

PrecisionINT64TYPES FALSE

PRECISION10 FALSE

DEFAULTPRECISION 32-bit

Schema CacheTLMINTERVAL 1

SDE error loggingERRLOGMODE TIC

Process statisticsPROCSTATS -1

Sets the precision mapping for the data. Note that > 32-bit geometries are currently notsupported with any ArcGIS clients (will be supported at future releases).


Server Parameters

LockingSTATEAUTOLOCKING FALSE

LAYERAUTOLOCKING FALSE

Autoregistration for spatial typesDISABLEAUTOREG TRUE

Sets the level of locking on features and states. Turned off by default.

Controls automatic registration of 3rd party spatial tables. Set to TRUE will increase the connection time to ArcSDE (since it will try to detect if there are any new un-registered tables).


Server Parameters

Detecting orphaned processesTCPKEEPALIVE FALSE TCPKEEPALIVE will tell

ArcSDE to test for defunct processes after a period of time (7200000ms or 2 hours by default). If a response is not received from the client at that time, the client process and associated information are cleaned up.

KB Article ID:25129


Error Logging

ArcSDE log files in etc folder (SDEHOME)

Sde_<instance>.log (sde process info)

Giomgr_<instance>.log (connection info)

Additional logging by setting environment variables:

SDEVERBOSE=TRUE

SDEINTERCEPTLOC=c:\temp\intercept.log

SDETRACELOC=c:\temp\sdetrace.log


ArcSDE Application Server

ArcSDE installed on the DBMS server

Shares OS resources (CPU, memory, disks) with the DBMS

ArcSDE Clients interact with ArcSDE server processes on tcp sockets

ArcSDEserver

ArcSDEclient app

DBMSserver


Remote ArcSDE

ArcSDE installed on a separate server (isolated from the DBMS tier)

Can connect to Non-supported DBMS platforms (e.g. Itanium)

ArcSDE processes run in own space, separated from the DBMS processes

ArcSDEgsrvr

GISclient

DBMSserver

Server 1

Server 2

Client


ArcSDE Direct Connect

ArcSDE server dlls run in the process space of the client (in-proc)

Remote Connection to the dbmsserver over the dbms network protocol

ArcSDEclient appArcSDE

server dlls

DBMSserver

Server

Client


Geodatabase Toolset


Geodatabase Toolset - Overview

Performance Investigation ToolsKnown contributors to performance problems

Convenient

Hosted within ArcMap and ArcCatalogClient (ArcMap) and Server (ArcCatalog)

Primary PurposeMonitoring

Preventive

Investigation


GDBT - ArcMap


Geodatabase Toolset - ArcMap

Data Fetching

Rendering Timer

Use whenWhich layer impacts ArcMap performance

Where is delay: Client(rendering) or Server(retrieval)



Scale and Layer VisibilityDo I need all those layers to be visible

When to useNeed to improve MXD performance

Reducing number of layers used


Geodatabase Toolset - ArcMapScripting

Simple scripting languageAutomates user activityScripts can be used with Enterprise Test Harness

Executed concurrently, sequentially on multiple computersLaptop, Desktop, Citrix, Terminal Servers

Pan/Zoom

WhenDuplicate activity of user panning and zoomingAcquire timing informationUse in conjunction with

layer visibility tabSQL Execute (tracing) tab



ScriptingAutomate ArcMap functionality

Define Edit Version

Create new features

Simple features

Geometric Networks

Topology

Edit existing features

Simple features

Geometric Networks

Topology



ScriptingEnable/Disable DBMS Trace

Define Edit Version

Create new features

Simple features

Geometric Networks

Topology

Edit existing features

Simple features

Geometric Networks

Topology



Scripting – WhenApply load on ArcSDE server

Test versioning workflow

DBMS Schema Relationships

Indexes

Attribute tables



SQL ExecuteOracle Tracing

Script Oracle tracing on all or portion of script

Name (modify) of trace file

SQLServerWorking on it

Execute SQL within DBMS environment

Uses Workspace connection of first layer in TOC

WhenNeed to determine DBMS behavior for specific ArcMap behavior

Pan/Zoom, Edit, Reconcile



Layer DescriptionDocument layers in TOC

When to useDocument MXD

Testing documentation

Providing information for support


GDBT - ArcCatalog


Geodatabase Toolset - ArcCatalog



Edit InformationCount of delta tables for versioned GDB objects

GDB characteristics

User InformationList of connected users

Workstation name

May be removed!



Table and Index Statistics



GDB Diagnostic ReportsVersion/State information

State count

Lineage count

Delta count (distinct) associated with V/S

State Object



GDB Diagnostic ReportsLayer Version/State information

State count

Delta count (distinct) associated with V/S

StateObject



GDB Diagnostic ReportsCompress Information

Compress Log

When compressed

Successful/UnSuccessful

Specific Lineage informationLength

Versions

Participating GDB Objects



GDB Diagnostic ReportsState/Version Integrity Check

State Table ID within Lineage

Lineage State within State

Version’s state in State Table and Lineage

Orphan’s

Psuedo-Compress report

Geodatabase Performance Factors and Tools - Amazon S3 · Geodatabase Performance Factors and Tools. ... ch er se Voltag e Re g Delivery P u l or H o t re e t ar y G ... Event monitor

Documents