rep704 effective use of replication server monitors and counters n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
REP704 Effective Use of Replication Server Monitors and Counters PowerPoint Presentation
Download Presentation
REP704 Effective Use of Replication Server Monitors and Counters

Loading in 2 Seconds...

play fullscreen
1 / 115

REP704 Effective Use of Replication Server Monitors and Counters - PowerPoint PPT Presentation


  • 114 Views
  • Uploaded on

REP704 Effective Use of Replication Server Monitors and Counters. Greg Carter Staff S/W Eng II - Development gcarter@sybase.com / (303)413-4067 08/05/2003. M&C Highlights. Introduced in release 12.1 New counters introduced with practically every release and EBF since

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'REP704 Effective Use of Replication Server Monitors and Counters' - hyman


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
rep704 effective use of replication server monitors and counters

REP704 Effective Use of Replication Server Monitors and Counters

Greg CarterStaff S/W Eng II - Developmentgcarter@sybase.com / (303)413-406708/05/2003

m c highlights
M&C Highlights
  • Introduced in release 12.1
  • New counters introduced with practically every release and EBF since
  • Statistics for single observation periods may be requested through the command line interface
  • Statistics for multiple observation periods may be captured in the RSSD
  • Statistics may be turned on or off by RepServer module
  • Statistics are divided into “intrusive” and “non-intrusive”
  • Supporting analysis tools available at http://repserver.codexchange.sybase.com/
m c goals
M&C Goals
  • Functional Monitoring
    • Internal Activity
    • Duplicate commands ignored
    • Total successful and failed transactions
    • Transaction group management
    • Transaction partitioning management
    • Command batch management
    • Thread yield and sleep times
    • Message movement across queues
    • Stable device segment management
    • SQT Transaction Queue management
    • SQT Cache management
    • RSSD activity
m c goals1
M&C Goals
  • Performance Monitoring
    • Bytes processed per time period
    • Network packets processed per time period
    • Commands processed per time period
    • Transactions processed per time period
    • Time required to send command batches or making RPCs
    • Time required to process command batch results
    • Time required to perform Function String mapping
    • Time required to check proper transaction sequencing
    • Stable queue write/read rates
m c goals2
M&C Goals
  • Configuration Profiling
    • Database operations without replication definitions
    • Database operations with no matching subscriptions
    • Lock deficiencies in the RDB
    • Transaction log space deficiencies in the RDB
    • Connection deficiencies in the RDB
    • Requests for rs_locater updates by the RepAgent
    • RepAgent connection packet size
m c goals3
M&C Goals
  • Transaction Profiling
    • Total begins, inserts, updates, deletes, commits, rollbacks
    • Total ungrouped transactions
    • Total “applied” and “request” commands
    • Total mini-abort commands
    • Average command size – includes replication overhead
    • Count and size of “large” commands
    • Commands per transaction
    • Memory consumption per transaction
m c goals4
M&C Goals
  • Tuning Support
    • Daemon thread scheduling
    • Command batch sizing
    • Transaction group sizing
    • Transaction partitioning
    • Sizing number of threads for parallel-DSI
    • Serialization method selection
    • Large transaction size selection
    • Thread scheduling management
    • SQM outstanding write request management
    • RSI queue truncation scheduling
    • Stable queue sizing
    • RSSD interaction control
    • Latency control in low volume systems
    • SQT cache sizing
    • STS cache sizing
repserver modules
RepServer Modules
  • Each counter is associated with a RepServer “module”
  • RepServer modules may be single or multi-instanced
  • Single-instanced modules include
    • CM – Connection Manager
    • STS – System Table Services
    • SYNC – Synchronization
  • Multi-instanced modules include
    • DIST – Distributor
    • DSI – Data Server Interface/Scheduler
    • DSIEXEC – Data Server Interface/Executor
    • REPAGENT – RepAgent Executor
    • RSI – RepServer Interface
    • SQM – Stable Queue Manager
    • SQMR – SQM Reader
    • SQT – Stable Queue Transaction Interface
    • SYNCELE – Synchronization Element
repserver modules1
RepServer Modules
  • For multi-instanced modules, counters are grouped by instance ID (for example, database ID) and optionally instance value (for example, DSI/E thread number when parallel DSI is enabled)
  • Notably absent are MEM (Memory Manager) and STSTAB (STS Table)
repserver modules2
RepServer Modules

Memory Manager

  • Memory Manager statistics available using “admin statistics, mem” and “admin statistics, mem_in_use”

1> admin statistics,mem

2> go

Segment_Size Number_of_Segments

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

256 36509

512 268502

1024 161082

2048 59558

4096 3507

8192 23

16384 9658

65536 26

1> admin statistics, mem_in_use

2> go

Memory_in_Use

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

621606401

repserver modules3
RepServer Modules

System Table Services

  • Some STSTAB statistics using debug commands

1> debug stscache,help

2> go

Please look at the log for output.

repserver modules4
RepServer Modules

System Table Services

T. 2003/07/01 09:52:00. (33): Usage: debug stscache, option, tablename, key, links

T. 2003/07/01 09:52:00. (33): Parameter 'option' (optional)

T. 2003/07/01 09:52:00. (33): ** default ** to print this help text

T. 2003/07/01 09:52:00. (33): "print" to print the cache

T. 2003/07/01 09:52:00. (33): "invalidate" to invalidate the cache

T. 2003/07/01 09:52:00. (33): "stats" to print cache statistics

T. 2003/07/01 09:52:00. (33): "fillcache" to fillcache with the specified object or all

objects

T. 2003/07/01 09:52:00. (33): "hitrate" to print cachehit-rate (STS_CACHESTATS trace

flag should be ON for this.

T. 2003/07/01 09:52:00. (33): "check" run some consistency checks on STS stuff.

T. 2003/07/01 09:52:01. (33): Parameter 'tablename' (optional)

T. 2003/07/01 09:52:01. (33): ** default ** all caches

T. 2003/07/01 09:52:01. (33): "all" all caches

T. 2003/07/01 09:52:01. (33): "rs_objects" rs_objects cache only

T. 2003/07/01 09:52:01. (33): Parameter 'key' (optional)

T. 2003/07/01 09:52:01. (33): ** default ** all objects

T. 2003/07/01 09:52:01. (33): "" all objects

T. 2003/07/01 09:52:01. (33): "tablekey" objects with significant key member = tablekey

T. 2003/07/01 09:52:01. (33): Parameter 'links' (optional)

T. 2003/07/01 09:52:01. (33): ** default ** link caches also

T. 2003/07/01 09:52:01. (33): "" link caches also

T. 2003/07/01 09:52:01. (33): "no_links" skip link caches

repserver modules5
RepServer Modules

System Table Services

1> debug stscache,stats

2> go

T. 2003/07/01 09:58:14. (33): Cache Statistics

T. 2003/07/01 09:58:14. (33): rs_columns: Link Cache

Obj_count = 91

Objects_In_use = 10

Valid = 91, Invalid = 0

on LRU = 0

T. 2003/07/01 09:58:14. (33): rs_columns: Primary Cache

Obj_count = 10

Objects_In_use = 1

Valid = 10, Invalid = 0

on LRU = 9

T. 2003/07/01 09:58:14. (33): rs_config: Primary Cache

Obj_count = 100

Objects_In_use = 0

Valid = 100, Invalid = 0

on LRU = 100

repserver modules6
RepServer Modules

System Table Services

I. 2003/07/01 09:39:43. Maximum outbound connections allowed: 128.

I. 2003/07/01 09:39:43. System outbound connection fadeout time: '30'.

I. 2003/07/01 09:39:43. System table cache size: 100 rows.

I. 2003/07/01 09:39:43. Maximum number of Open Server threads allowed: 50.

I. 2003/07/01 09:39:43. Maximum number of Open Server mutexes allowed: 1024.

I. 2003/07/01 09:39:49. A cached row for system table 'rs_config' was swapped ou

t of the cache in order to accomodate another row. If this message appears mult

iple times it may be advisable to increase sts_cachesize from its present value

of '100'.

repserver modules7
RepServer Modules

System Table Services

1> trace 'on', 'sts','sts_cachestats'

2> go

1> debug stscache,hitrate

2> go

Please look at the log for output.

repserver modules8
RepServer Modules

System Table Services

I. 2003/07/01 10:29:23. Trace enabled 'sts', 'sts_cachestats'.

T. 2003/07/01 10:29:32. (30): Cache Hit Rate:

T. 2003/07/01 10:29:32. (30): tablename hit miss miss_hit

miss_miss

T. 2003/07/01 10:29:32. (30): --------- --- ---- --------

---------

T. 2003/07/01 10:32:45. (30): rs_classes 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_columns 122098 0 0 0

T. 2003/07/01 10:32:45. (30): rs_config 3898 3272 0 3272

T. 2003/07/01 10:32:45. (30): rs_datatype 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_databases 1343 0 0 0

T. 2003/07/01 10:32:45. (30): rs_diskaffinity 0 31 0 31

T. 2003/07/01 10:32:45. (30): rs_functions 25253 0 0 0

T. 2003/07/01 10:32:45. (30): rs_locater 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_objects 54585 1 0 1

T. 2003/07/01 10:32:45. (30): rs_queues 2775 0 0 0

T. 2003/07/01 10:32:45. (30): rs_repdbs 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_routes 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_sites 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_systext 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_translation 0 159 0 159

T. 2003/07/01 10:32:45. (30): rs_users 32 0 0 0

T. 2003/07/01 10:32:45. (30): rs_repobjs 0 0 0 5126

T. 2003/07/01 10:32:45. (30): rs_version 0 0 0 0

T. 2003/07/01 10:32:45. (30): rs_publications 0 0 0 0

repserver modules9
RepServer Modules

Message Delivery

  • MD stats available independent of M&C

1> admin statistics,md

2> go

Source Pending_Messages Memory_Currently_Used

Messages_Delivered SQM_Writes Destinations_Delivered_To

Max_Memory_Hit Is_RSI_Source?

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

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

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

pds01 43 12716

24376 24376 0

0 0

repserver modules10
RepServer Modules
  • Current stats for all instances of all modules except STSTAB are displayed by using “admin statistics,all_modules”
  • Since “admin statistics,all_modules” displays stats for all instances of SYNCELE, a lot of output is generated, much of which is not useful to customers
counter documentation
Counter Documentation
  • The best source of information on specific counters is in the RSSD, accessed via the rs_helpcounter stored procedure

1> rs_helpcounter

2> go

ModuleName

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

CM

DIST

...

SYNCELE

How to Use rs_helpcounter

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

rs_helpcounter [intrusive | sysmon | rate | duration | internal

| must_sample | no_reset | keep_old | configure]

rs_helpcounter ModuleName [, {type | short | long}]

rs_helpcounter keyword [, {type | short | long}]

counter documentation1
Counter Documentation

Counter Types

  • Total – Accumulate a running total
  • Average – Calculate the average of the total over the number of observations sample period
  • Maximum – Record the maximum value observed over the sample period
  • Last – Record the last observed value for the sample period

1> rs_helpcounter sqm,type

2> go

Display Name Module Name Counter Type Counter Status

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

AffinityHintUsed SQM Total 00000000

BPSaverage SQM Average 00000044

BPScurrent SQM Last 00000040

BPSmax SQM Maximum 00000040

BlocksFullWrite SQM Total 0000008C

BlocksRead SQM Total 00000088

BlocksReadCached SQM Total 00000088

...

counter documentation2
Counter Documentation

Counter Statuses

  • Configure – Runtime configuration setting. Not implemented.
  • Internal – Internal support. Not available in the RSSD.
  • Keep old – Current a previous sample period values are retained
  • No reset – The counter is not reset when executing the “admin statistics, reset” command
  • Must sample – The counter must collect data even if sampling has been turned off
  • Intrusive – Because of the nature of the counter, setting it on for sampling may negatively impact performance
  • Sysmon – The counter is reported by the “admin statistics, sysmon” command
  • Rate – Counter results are reported as a rate usually expressed in terms of number of observations per second
  • Duration – Counter results are reported as a length of time usually expressed in 100ths of a second
counter documentation3
Counter Documentation

1> rs_helpcounter BlocksReadCached,short

2> go

Display Name Module Name

Counter Description

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

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

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

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

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

BlocksReadCached SQM

Obsolete. See CNT_SQMR_BLOCKS_READ_CACHED.

BlocksReadCached SQMR

Total number of 16K blocks from cache read by an SQM Reader thread.

counter documentation4
Counter Documentation

1> rs_helpcounter BlocksReadCached,long

2> go

counter_id counter_name

module_name display_name

counter_type counter_status

description

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

6010 SQM: Blocks read from cache

SQM BlocksReadCached

1 136

Obsolete. See CNT_SQMR_BLOCKS_READ_CACHED.

62004 SQMR: Blocks read from cache

SQMR BlocksReadCached

1 140

Total number of 16K blocks from cache read by an SQM Reader thread.

statistics configurations
Statistics Configurations
  • All statistics related configurations are dynamic. That is, they take effect immediately, not requiring a RepServer re-boot.
  • The following RepServer-wide configurations set with “configure replication server” are persistent
    • stats_reset_afterflush – should counters be reset after flushing, default is “on”
    • stats_daemon_sleep_time – each time the Statistics Daemon awakens, it calculates any “rate” counters and flushes counters to the RSSD if RSSD flushing is configured, default is “120” seconds
    • stats_flush_rssd – should counters be flushed to the RSSD, default is “off”
    • stats_sampling – should counters be actively collecting data, default is “on”
  • The following RepServer-wide configurations are transient
    • stats_intrusive_counter – should intrusive counters be actively sampling data, default is “off”. Set with “admin stats_intrusive_counter, ['off‘|’on’]
statistics configurations1
Statistics Configurations

Module Flushing Statuses

  • Module, connection and route flushing status configurations are all transient and all off by default
  • [BUG?] Configuring module, connection or route flushing statuses requires that both “stats_sampling” and “stats_flush_rssd” be turned on
  • In order to view statistics either by flushing them to a client connection using “admin statistics, sysmon” or by flushing them to the RSSD, you must turn the flushing status on for the modules desired
  • Configuring flushing status for all modules
    • admin stats_config_module, { module | all_modules } , { 'on' | 'off ' }
    • [BUG?]Valid for all modules except DSIEXEC and SQMR which should be set the same as DSI and SQM respectively
    • [BUG?] Multi-instanced module SYNCELE is configured independently of single-instanced module SYNC using “admin stats_config_connection”
statistics configurations2
Statistics Configurations

Module Flushing Statuses

  • Configuring flushing status for multi-instanced modules
    • admin stats_config_connection, { data_server, database | all_connections } , {module | all_modules } , [ 'inbound' | 'outbound' ] {'on' | 'off' }
      • Valid for modules DSI, SQM, SQT, DIST and REPAGENT
      • “inbound”/”outbound” option only valid for modules SQM and SQT
      • [BUG?]Valid for all modules except DSIEXEC and SQMR which should be set the same as DSI and SQM respectively
      • [BUG?] When “all_modules” is specified, SYNCELE flushing status is configured
statistics configurations3
Statistics Configurations

Module Flushing Statuses

  • admin stats_config_route, {rep_server | 'all_routes' }, {module | all_modules} , {'on' | 'off ' }
    • “rep_server” is a RepServer to which this one has a route
    • Valid for modules RSI and SQM
statistics configurations4
Statistics Configurations

Module Flushing Statuses

1> admin statistics, flush_status

2> go

RepServer RSSD flushing status for prs01 ran on: 07/10/03 11:10:38 AM

Rep Server Counters Flush Configuration.

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

Configuration_Name Run_Value

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

stats_daemon_sleep_time 600

stats_sampling on

stats_flush_rssd off

stats_reset_afterflush on

stats_intrusive_counter off

Rep Server module flushing status.

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

Module_Name Info Flush_Status

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

CM off

DIST off

DSI off

statistics configurations5
Statistics Configurations
  • admin statistics, reset
    • Resets all counters that are allowed to be reset
    • Enables a “clean start” at the beginning of a sample period
    • Counter resets are automatically done at the start of each “admin statistics, sysmon” execution
    • Counter resets are automatically done at the end of each RSSD flush if “stats_reset_afterflush “ has been set on (default)
steps to collect statistics
Steps to Collect Statistics
  • Decide whether to flush stats to the client connection using “admin statistics, sysmon” or to the RSSD
  • Set flushing status for modules appropriately
  • Decide whether to include “intrusive” counters
  • Began sampling and collecting results
collecting stats with m c
Collecting Stats with M&C

Using a Client Connection

  • Using a client connection such as with isql, you can configure for and collect statistics using the “admin statistics, sysmon” command
  • With “admin statistics, sysmon” only those counters with “sysmon” status will be flushed – see RSSD stored procedure “rs_helpcounter sysmon”
  • “admin statistics, sysmon” takes a number of seconds for the sample period, default is 1 – Ex. “admin statistics, sysmon, 300” for a 300 second or 5 minute sample period
  • “admin statistics, sysmon” blocks the client session until the sample period has expired at which point all “sysmon” counters for flush enabled modules will be written to the client
  • “admin statistics, sysmon” forces a counter reset prior to the start of the sample period
collecting stats with m c1
Collecting Stats with M&C

Using a Client Connection

1> admin statistics,sysmon

2> go

Sybase Replication Server Statistics Report

===============================================================================

RepServer Version: Replication Server/12.5/SMP EBF 10999/Sun_svr4/OS

5.8/1/DEBUG/Fri Apr 11 01:19:59 PDT 2003

Open Server Version: Sybase Server-Library/12.5/P-EBF10880-10879

ESD#9/DRV.12.5.0.6/SPARC/Solaris 2.8 Native Threads/BUILD125-026/OPT/Sun Jan 12

10:30:48 2003

Open CLient Version: Sybase Client-Library/12.5/P-EBF10879

ESD#9/DRV.12.5.0.6/SPARC/Solaris 2.8 Native Threads/BUILD125-026/OPT/Sun Jan 12

10:28:05 2003

RepServer Name: prs01

Start Date: 07/10/03 12:17:59 PM

End Date: 07/10/03 12:18:01 PM

Sample Interval (secs): 2

===============================================================================

collecting stats with m c2
Collecting Stats with M&C

Using a Client Connection

RepServer Runtime Configurations

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

memory_limit: 900

init_sqm_write_delay: 1000

init_sqm_write_max_delay: 10000

sqm_write_flush: off

sqt_max_cache_size: 209715200

sqt_init_read_delay: 2000

sqt_max_read_delay: 10000

...

========================================================================

collecting stats with m c3
Collecting Stats with M&C

Using a Client Connection

1> configure replication server

2> set stats_flush_rssd to 'on'

3> go

Config parameter 'stats_flush_rssd' is modified.

  • Must do this to configure module flushing status even though we are not wanting to flush to the RSSD

1> admin stats_config_module,sqt,'on'

2> go

1> configure replication server

2> set stats_flush_rssd to 'off'

3> go

Config parameter 'stats_flush_rssd' is modified.

collecting stats with m c4
Collecting Stats with M&C

Using a Client Connection

1> admin statistics, flush_status

2> go

...

Rep Server module flushing status.

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

Module_Name Info Flush_Status

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

CM off

DIST off

DSI off

REPAGENT off

RSI off

SQM off

SQT 101:0 DSI 101 edsprs01.edbprs01 off [BUG?]

SQT 102:0 DSI 102 pds01.tpcc off

SQT 104:0 DSI 104 rds01.tpcc off

SQT 103:0 DSI 103 wsb01.tpcc off

SQT 102:1 DIST pds01.tpcc off

STS off

SYNC off

SYNCELE off

collecting stats with m c5
Collecting Stats with M&C

Using a Client Connection

1> admin statistics,sysmon,60

...

SQT Statistics

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

Info Instance_ID Instance_Val CmdsTotal

OpenTransTotal CmdsAveTran CacheMemUsed MemUsedMaxTran MemUsedAveTran

TransRemoved TruncTransTotal ClosedTransTotal ReadTransTotal

OpenTransRmTotal TruncTransRmTotal ClosedTransRmTotal ReadTransRmTotal

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

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

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

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

...

104:0 DSI 104 rds01.tpcc 104 0 1985

131 15 104859136 18204 7563

0 131 153 148

131 127 148 149

103:0 DSI 103 wsb01.tpcc 103 0 2240

141 15 104858368 46592 19234

0 141 170 181

141 152 181 181

102:1 DIST pds01.tpcc 102 1 12302

815 15 104858368 46620 18137

0 815 815 804

815 804 804 804

collecting stats with m c6
Collecting Stats with M&C

Using a Client Connection

1> configure replication server

2> set stats_flush_rssd to 'on'

3> go

Config parameter 'stats_flush_rssd' is modified.

  • Again, we must do this to configure module flushing status even though we are not wanting to flush to the RSSD

1> admin stats_config_connection,all_connections,sqm,'on'

2> go

1> configure replication server

2> set stats_flush_rssd to 'off'

3> go

Config parameter 'stats_flush_rssd' is modified.

collecting stats with m c7
Collecting Stats with M&C

Using a Client Connection

1> admin statistics,flush_status

...

Module_Name Info Flush_Status

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

CM off

DIST off

DSI off

REPAGENT off

RSI off

SQM 101:0 edsprs01.edbprs01 on

SQM 102:0 pds01.tpcc on

SQM 102:1 pds01.tpcc on

SQM 104:0 rds01.tpcc on

SQT off

STS off

SYNC off

SYNCELE off

collecting stats with m c8
Collecting Stats with M&C

Using a Client Connection

1> admin statistics,sysmon,120

...

SQM Statistics

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

Info Instance_ID Instance_Val CmdsWritten

BlocksWritten BytesWritten SegsActive SegsAllocated SegsDeallocated

UpdsRsoqid WritesTimerPop WriteRequests BlocksFullWrite BPSaverage

CmdSizeAverage

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

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

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

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

...

102:1 pds01.tpcc 102 1 21582

1486 23187074 126 24 5

24 10 21582 1476 0

957

104:0 rds01.tpcc 104 0 20469

466 7448675 45 7 1

7 8 20469 458 0

246

collecting stats with m c9
Collecting Stats with M&C

Capturing Stats in the RSSD

  • RSSD Tables Involved
    • rs_statcounters: Descriptive information about each counter. Contents are static but may change with each release or EBF
    • rs_statrun: One row per sampling period. Ties together all counter values for a given sampling period.
    • rs_statdetail: Counter values
  • By default counters are reset after being flushed to the RSSD in anticipation of immediately collecting data for the next sampling period
  • You can alter that behavior by setting “stats_reset_afterflush” to off. This RepServer configuration is persistent.
collecting stats with m c10
Collecting Stats with M&C

Capturing Stats in the RSSD

  • Make sure
    • 'stats_sampling' set to 'on‘ (default)
    • 'stats_flush_rssd' set to 'on‘ (not the default)
    • 'stats_reset_afterflush' set to 'on‘ (default)
  • Choose setting for
    • 'stats_daemon_sleep_time' - default is '120‘ or 2 minutes
    • ‘stats_intrusive_counter’ - default is ‘off’
    • ‘stats_config_module’ – recommend “all_modules, 'on‘”
    • ‘stats_config_connection’ – recommend “all_connections, all_modules, 'on‘”
    • ‘stats_config_route’ – recommend “all_routes, all_modules, ‘on’”
  • Clean out any statistics from earlier RSSD statistics flushes
    • Set 'stats_flush_rssd' set to 'off‘
    • Truncate RSSD tables rs_statdetail and rs_statrun
    • Set 'stats_flush_rssd' set to 'on‘
  • You are now collecting statistics in the RSSD
collecting stats with m c11
Collecting Stats with M&C

Capturing Stats in the RSSD

  • When you’ve got what you want, make sure
    • 'stats_flush_rssd' set to 'off‘ (default)
    • ‘stats_intrusive_counter’ set to ‘off’
    • ‘stats_config_module’ set to “all_modules, 'off‘”
    • ‘stats_config_connection’ set to “all_connections, all_modules, 'off‘”
    • ‘stats_config_route’ set to “all_routes, all_modules, ‘off’”
  • To dump statistics out of the RSSD into a CSV file
    • Used RSSD stored procedure “rs_dump_stats”
    • “rs_dump_stats” is currently only available from script “stats_crt_dump_stats” located at the “SDN CodeXchange” web site at http://www.codexchange.sybase.com/servlets/DomainHome. Look under RepServer, Performance Management, Reference Implementation, RepPerfRefImpl.zip.
collecting stats with m c12
Collecting Stats with M&C

Capturing Stats in the RSSD

  • Sample of “rs_dump_stats” output

Comment: Sample Run

May 6 2003 2:54:05:653AM

May 6 2003 4:34:47:920AM

51

2

16384

64

SQM

102

1

102:1 pds01.tpcc

SQM: Commands written to queue

CmdsWritten

6000 , , 102, 1

May 6 2003 2:54:05:653AM, 49926

May 6 2003 2:56:06:990AM, 17088

May 6 2003 2:58:08:256AM, 10888

interpreting and using m c stats
Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

  • M&C Analysis spread sheets are currently only available from the “SDN CodeXchange” web site at http://www.codexchange.sybase.com/servlets/DomainHome. Look under RepServer, Performance Management, Monitors Counters Analysis , MonCounters-Analysis.zip.
  • The spread sheets present summaries and charts based on the CSV file created by “rs_dump_stats”
  • If a chart is not drawn, there is no data for the associated counter
slide45

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

1

2

3

Locate the data file generated by rs_dump_stats.

slide46

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

Using the “Text Import” Wizard, select “Delimited” and <Next>

slide47

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

For “Delimiters”, check “Comma” and choose <Finish>

slide48

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

The data will load into a new worksheet looking something like this. Move it into the workbook containing the analysis spreadsheets.

interpreting and using m c stats1
Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

  • If the rows in the data file exceed Excel’s limit (65k)
    • You can chop the one data file into multiple data files
    • Usually best to break on module boundaries
    • Each data file must have the following rows at top:and this one at the bottom:
interpreting and using m c stats2
Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

REPAGENT Summary

interpreting and using m c stats3
Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

REPAGENT – 58000: CmdsTotal

6 minute intervals

Determined by setting of

stats_daemon_sleep_time

slide52

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

REPAGENT – 58001-58009: CmdsApplied, CmdsRequest, CmdsSystem, CmdsMiniAbort, CmdsDumpLoadDB, CmdsPurgeOpen, CmdsRouteRCL, CmdsEnRepMarker, UpdsRslocater

slide53

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQM Writer Summary

slide54

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQM – 6002: BlocksWritten, 6041: BlocksFullWrite

slide55

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQM – 6020: SegsActive, 6021: SegsAllocated, 6022: SegsDeallocated

slide56

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQM – 6023: TimeLastNewSeg, 6025: TimeMaxNewSeg, 6027: TimeAveNewSeg

slide57

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQM – 6029: TimeLastSeg, 6031: TimeMaxSeg, 6033: TimeAveSeg

slide58

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQMR Summary

slide59

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

SQM – 6002: BlocksWritten, SQMR – 62002: BlocksRead, 62004: BlocksReadCached

slide60

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DIST Summary

slide61

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DIST – 30024: TDbegin, 30025: TDclose, 30020: SREstmtsInsert, 30021: SREstmtsUpdate, 30022: SREstmtsDelete, 30010: CmdsDump, 30011: CmdsMarker

slide62

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DSI/S Summary

slide63

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DSI/S – 5013: TranTimeLast, 5015: TranTimeMax, 5017: TranTimeAve

slide64

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DSI/E Summary

slide65

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DSI/E – 57074: DSIEBatchTimeAve, 57112: DSIESCBTimeAve, 57041: SendTimeAvg, 57067: DSIEResultRimeAve, 57106: DSIESCCTimeAve

slide66

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DSI/E – 57000: TransApplied for all DSI/E threads

slide67

Interpreting and Using M&C Stats

Using M&C Analysis Spread Sheets

DSI/E – 57000: TransApplied for all DSI/E threads

interpreting and using m c stats4
Interpreting and Using M&C Stats

For Functional Monitoring - REPAGENT

slide69

Interpreting and Using M&C Stats

For Functional Monitoring - SQM

slide70

Interpreting and Using M&C Stats

For Functional Monitoring - SQM

slide71

Interpreting and Using M&C Stats

For Functional Monitoring - SQMR

slide72

Interpreting and Using M&C Stats

For Functional Monitoring - SQT

slide73

Interpreting and Using M&C Stats

For Functional Monitoring - SQT

slide74

Interpreting and Using M&C Stats

For Functional Monitoring - DIST

slide75

Interpreting and Using M&C Stats

For Functional Monitoring – DSI

slide76

Interpreting and Using M&C Stats

For Functional Monitoring – DSI

slide77

Interpreting and Using M&C Stats

For Functional Monitoring – DSI

slide78

Interpreting and Using M&C Stats

For Functional Monitoring – DSIEXEC

slide79

Interpreting and Using M&C Stats

For Functional Monitoring – RSI

slide80

Interpreting and Using M&C Stats

For Functional Monitoring – STS

interpreting and using m c stats5
Interpreting and Using M&C Stats

For Configuration Profiling

interpreting and using m c stats6
Interpreting and Using M&C Stats

For Transaction Profiling - REPAGENT

slide83

Interpreting and Using M&C Stats

For Transaction Profiling - SQM

slide84

Interpreting and Using M&C Stats

For Transaction Profiling - SQT

slide85

Interpreting and Using M&C Stats

For Transaction Profiling - DIST

slide86

Interpreting and Using M&C Stats

For Transaction Profiling - DSI

slide87

Interpreting and Using M&C Stats

For Transaction Profiling - DSIEXEC

interpreting and using m c stats7
Interpreting and Using M&C Stats

For Performance Monitoring - REPAGENT

slide89

Interpreting and Using M&C Stats

For Performance Monitoring - SQM

slide90

Interpreting and Using M&C Stats

For Performance Monitoring - SQMR

slide91

Interpreting and Using M&C Stats

For Performance Monitoring - SQT

slide92

Interpreting and Using M&C Stats

For Performance Monitoring - DIST

slide93

Interpreting and Using M&C Stats

For Performance Monitoring - DSI

slide94

Interpreting and Using M&C Stats

For Performance Monitoring - DSIEXEC

slide95

Interpreting and Using M&C Stats

For Performance Monitoring - DSIEXEC

slide96

Interpreting and Using M&C Stats

For Performance Monitoring - DSIEXEC

slide97

Interpreting and Using M&C Stats

For Performance Monitoring - RSI

interpreting and using m c stats8
Interpreting and Using M&C Stats

For Tuning Support - REPAGENT

slide99

Interpreting and Using M&C Stats

For Tuning Support - SQM

slide100

Interpreting and Using M&C Stats

For Tuning Support - SQM

slide101

Interpreting and Using M&C Stats

For Tuning Support - SQT

slide102

Interpreting and Using M&C Stats

For Tuning Support - DSI

slide103

Interpreting and Using M&C Stats

For Tuning Support - DSI

slide104

Interpreting and Using M&C Stats

For Tuning Support - DSI

slide105

Interpreting and Using M&C Stats

For Tuning Support - DSI

slide106

Interpreting and Using M&C Stats

For Tuning Support - DSIEXEC

slide107

Interpreting and Using M&C Stats

For Tuning Support - RSI

slide108

Interpreting and Using M&C Stats

For Tuning Support - STS

slide109

Interpreting and Using M&C Stats

Looking at Some Details

  • Q1 is inbound, Q2 is outbound
  • Note observation points 25, 74, 76, 80
  • When one task finishes, the others speed up
slide110

Interpreting and Using M&C Stats

Looking at Some Details

slide111

Interpreting and Using M&C Stats

Looking at Some Details

slide112

Interpreting and Using M&C Stats

Looking at Some Details

  • Similar to Titus results, but OBQ processing, writes vs reads, align pretty closely.
slide113

Interpreting and Using M&C Stats

Looking at Some Details

  • Contention for processing time has been removed.
things about m c to consider
Things About M&C to Consider
  • Counter accumulations do not stop during flushing
  • Counter resets are not synchronized with counter accumulation
  • When flushing to the RSSD, all counters are flushed and then all counters are reset
  • For the above reasons, the larger the sample period, the smaller the relative margin of error