– show stat
Show Stat 은 memory, trading, concurrent users, disk space, mail services, copy services, network activities 등 여러가지 관련된 통계리포팅을 제공함성능을 모니터링하고 퍼포먼스 이슈에 대해 파악하기 위해 아래 명령어를 사용권장
(1) show stat Server.Trans.PerMinute: 1분동안 일어난 트랜잭션수
(2) show stat Server.Users *: active sessions 수 (연결된 사용자, 시스템수, 복제 및 서비스 태스크 포함)
(3) show stat Server.Sessions.Dropped: 응답시간 지연으로 연결이 해제된 수
(4) show stat Domino
(5) 그외 다른 서비스에 관한 내용을 모니터링 하기위해선 아래와 같은 명령어를 사용
show stat SMTP
show stat POP3
show stat IMAP
show stat LDAP
– show stat server
Server.ConcurrentTasks – identifies the number of server tasks (transactions) that are currently executing.
Server.ConcurrentTasks.Max – identifies the highest number of server tasks (transactions) that were concurrently executing at one point in time.
Server.ConcurrentTasks.Waiting – identifies the number of server tasks (transactions) that are awaiting execution because the maximum number of concurrent tasks has been reached.
Server.ConcurrentTasks.Waiting.Max – identifies the highest number of server tasks (transactions) that were awaiting execution at one point in time because the maximum number of concurrent tasks has been reached.
>Users
Server.Users < Server.Users.1MinPeak 인 이유는… 1 client can open more than 1 session 이기 때문
Server.Users = 157
Server.Users.1MinPeak = 284
Server.Users.1MinPeakTime = 03/23/2006 13:07:38 ZE8
Server.Users.5MinPeak = 425
Server.Users.5MinPeakTime = 04/06/2006 12:53:57 ZE8
Server.Users.Active = 9
Server.Users.Active15Min = 130
Server.Users.Active1Min = 41
Server.Users.Active30Min = 163
Server.Users.Active3Min = 73
Server.Users.Active5Min = 91
Server.Users.Peak = 1282
Server.Users.Peak.Time = 04/06/2006 12:49:49 ZE8
– show stat Database.
SHOW STAT DATABASE 명령어로 서버가 NSF buffer pool 을 모니터링 가능함
> DB buffer pool
DB buffer pool size 는 32bit 시스템에서는 최대 512MB 이며 64bit 시스템에서는 1024MB 임
Database.Database.BufferPool.Maximum.Megabytes = 512 // 최대 설정된값
Database.Database.BufferPool.MM.Reads = 40
Database.Database.BufferPool.MM.Writes = 68
Database.Database.BufferPool.Peak.Megabytes = 510 // 피크치 사용된 메모리양
Database.Database.BufferPool.PerCentReadsInBuffer = 97.54
만약 BufferPoolPeak (Peak.Megabytes/Maximum.Megabytes)가 주기적으로 95% 이상일경우 NSF_Buffer_Pool_Size 를 증가시켜줄 필요가 있음.
Database.BufferPool.PerCentReadsInBuffer 값을 확인할때 매우 많은 워크로드가 걸리는 경우는 BufferPoolPeak 가 100%를 나타날때 PerCentReadsInBuffer 값이 95% 이하임. PerCentReadsInBuffer 값이 낮으면 메모리가 충분하지 않아 생길 수 있음.
매우 적은 워크로드일경우 BufferPoolPeak 가 10% 이하이며 이때 PerCentReadsInBuffer 97% 이상임
>DBCache
현재 DBCache 갯수가 최대 갯수를 초과할경우, Rejections 가 발생됨
Database.DbCache.CurrentEntries = 2304 // 현재 DBCache 갯수
Database.DbCache.DatabaseLinkEntries = 0
Database.DbCache.HighWaterMark = 2304
Database.DbCache.Hits = 611819
Database.DbCache.InitialDbOpens = 746590
Database.DbCache.Lookups = 1703345
Database.DbCache.MaxBucketLength = 7
Database.DbCache.MaxEntries = 1536 //최대 DBCache 갯수
Database.DbCache.NumBuckets = 1543
Database.DbCache.NumBucketsUsed = 1160
Database.DbCache.OvercrowdingRejections = 115436
Database.DbCache.Size = 5011
>nlcache
아래 경우는 32 MB 일경우 부족함. 최대 64MB 로 올리고 상태를 확인해야함.
Notes.ini 에서 NLCache_Size=67108864 설정(64MB)
Database.NAMELookupCacheCacheSize = 21,935,408
Database.NAMELookupCacheHashSize = 1,839,223
Database.NAMELookupCacheHits = 339,764
Database.NAMELookupCacheLookups = 966,256
Database.NAMELookupCacheMaxSize = 33,554,432 //32MB
Database.NAMELookupCacheMisses = 322,092
Database.NAMELookupCacheMisses.ItemMisses = 276,533
Database.NAMELookupCacheNoHitHits = 304,400
Database.NAMELookupCachePool.Peak = 33,554,432
Database.NAMELookupCachePool.Used = 33,512,864
Database.NAMELookupCacheResets = 0
Database.NAMELookupCache.ContainerResets = 0
Database.NAMELookupCache.CriticalContainerResets = 0
Database.NAMELookupCache.EligibleContainerResets = 0
Database.NAMELookupMisses = 16,225
Database.NAMELookupTotal = 879085
Database.NAMELookupTotalLookupTime = 2,460.258
– show stat http
Http.Accept.ConnectionsAccepted = 1783
Http.Accept.ConnectionsDenied = 0
Http.Accept.ConnectionsRefused = 0
Http.Accept.Errors = 0
Http.Accept.Polls = 4105 // 정상적인 상황
Http.Accept.PollTimeouts = 2321
Http.Accept.ServerBusy = 182 // Thread 갯수가 모두찬 상태가 몇번인지 확인
Http.CurrentConnections = 22 //현재 Session 갯수
Http.MaxConnections = 40 // 최대 Session 갯수
Http.PeakConnections = 40 // 피크시 Session 갯수
Http.Workers = 40 // active number of threads Domino 서버문서 (internet Protocol -> HTTP) 에서 설정
IdleSessionTimeout
InputTimeout
OutputTimeout
– show dbs
Domino database 별로 관련된 통계정보를 제공해줌.
“LockWaits” 과”AvgWait” 값을 수집하기 위해서 notes.ini 파일에 아래의 설정을 추가해야함:
COLLECT_DB_LOCK_WAITS = 1
* 시스템 리소스를 소비하기 때문에 확인필요.
– platform-related statistical reports (statistical reports):
PLATFORM_STATISTICS_ENABLED = 1 설정
Platform.System.TotalUtil. * – Average CPU usage statistics information system, including processing all Domino and non-Domino jobs jobs.
(Platform.System.PctCombinedCpuUtil)
Platform.Process. * – Indicates that a single specific Domino Domino server tasks CPU usage
Platform.Memory. * – Memory statistics. (Platform.Memory.RAM.TotalMBytes)
Platform.Network. * – Network statictics. (Platform.Network.Total.PctUtilBandwidth)
Platform.LogicalDisk. * – Use entire disk i Series Statistics (All configure disks in all ASPs)
>Pct
Platform.System.PctCombinedCpuUtil = 0.95
Platform.System.PctTotalPrivilegedCpuUtil = 0.56
Platform.System.PctTotalUserCpuUtil = 0.4
>Process
Platform.Process.http.1.DominoLocalFreeKBytes = 658
Platform.Process.http.1.DominoSharedFreeKBytes = 48,329
Platform.Process.http.1.MemFreeKBytes = 8,588,265,092
Platform.Process.http.1.MemUsedKBytes = 176,164
Platform.Process.http.1.PctCpuUtil = 0
Platform.Process.http.1.PgFaultsPerSec = 0
Platform.Process.http.1.ProcessID = 4052
Platform.Process.http.1.VMSizeKBytes = 235,628
– show tran
Center for each running Domino transaction reports provide performance statistics by analyzing the results, you can decide whether to trade requires more CPU resources to complete.
In general, a good transaction response time should be less than 1000 milliseconds; while the transaction is greater than 5000 milliseconds response speed is poor.
영업부 
Inspiration 