Best Practices

for Domino Server and

Application Tuning

Francie Tanner
panagenda
2011 Wellesley Information Services. All rights reserved.

What Well Cover

Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

1
In This Session Were Going To
Learn how to configure your hardware, operating system, and
Domino servers and applications so they can perform their best

Gett the
G th tools
t l tto h
help
l you id
identify
tif whats
h t slowing
l i your servers
down

Find out how to keep your data healthy and corruption free
And if that didnt work how to resolve corruption

Get a firm understanding how to effectively monitor your servers

and prevent issues before they occur

Why You Might Care About What I Say

Principal Consultant and Director for panagenda

Over 14 years experience with Domino environments

Managing,
M i architecting,
hit ti and d supporting
ti

Various site/version/size deployments

10 to 100,000 users

Versions 4-8

Experienced Lotus instructor and speaker

Pretty good administrator and end user, too

Bunch o certifications
3
The Cost of NOT Maintaining Your Servers and Data
Bad server performance
Agents dont finish running in time

Applications open slowly

Unhappy users

Corruption can occur

Users are denied access to applications

View indexes are not up to date

Or get rebuilt just as users want to use them

M i t
Maintenance tasks
t k dont
d t finish
fi i h over night
i ht
Users are unable to open their mail in the morning

What Well Cover

Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

5
Optimizing Your Hardware
Hardware isnt everything
But you can avoid performance bottlenecks here

Processor speed and utilization affects how fast Domino runs

Faster CPU doesnt always mean a faster server

f Put everything on the same slow disks and this wont help

More RAM is better to a certain point

Affects simultaneous Notes sessions and more

Drive cache
Optimize
O ti i this
thi especially
i ll if youre
going
i to
t let
l t your OS
manage this

Optimizing Your Operating System

Make sure your anti-virus software is properly configured to work
with Dominos constantly open files
The alternative is disastrous

U a 64-bit
Use 64 bit OS,
OS if possible,
ibl as it has
h more capabilities
biliti
Even with 32-bit Domino code

But be sure to check if its compatible with extended products,

such as Sametime, Traveler, etc.
Use DDM Operating system probes to constantly measure and
evaluate yyour servers
CPU probe

Disk probe

Memory probe

Network probe
7
Disk Input/Output Bottlenecks
Domino is extremely read and write intensive
Disk access rates and configuration affects Domino profusely

This is typically the number one issue slowing servers down

Get the fastest disks you can afford

DO NOT use one set of disks for everything

Instead, put the OS and Domino program directory on mirrored
drives
Domino data on a set of separately controlled RAID disks

DO use transaction logging whenever possible

Put the logs on yet another set of disks from the above
mentioned disks
Deal with eventual defragmentation of data
With appropriate tools please and Domino down
8

Disk Input/Output Bottlenecks (cont.)

If you use a SAN, make sure its properly configured and
optimized for Domino
Still try to keep transaction logs and view index rebuild
directories on local drives
f Look at the Resource section for more info

Move your view indexing temporary files to another drive

View_Rebuild_Dir=<directory path>

Dont confuse different partitions with different spindles

Drives that share the same read
read-write
write head and are impacted as
a unit
f Separate your data directory at the very least, if possible

9
Domino Software Tuning Version 8
You do not need to adjust the following as the UMB/NSF Buffer
Pool is automatically set to 512MB on 32-bit Domino and 1024MB
on 64-bit
PercentAvailSysResources

ConstrainedSHM, ConstrainedSHMSizeMB

MEMAddressableMem, MEMAddressableMemSizeMB

MEM_EnablePreAlloc, MEM_EnableSubAlloc

NSF_Buffer_Pool_Size_MB

f All of the above get set by default but some variables will still
get honored

10

Domino Software Tuning < 8

NSF_Buffer_Pool_Size_MB=(number in MB)
Controls the size of the NSF Buffer Pool, a section of memory
dedicated to buffering I/O transfers between the NIF indexing
functions and disk storage

NSF_DbCache_Maxentries=(number)
Can improve server performance by increasing the number of
databases that Domino can cache in memory at one time
Only
y modifyy if yyour server has sufficient memoryy

ConstrainedSHMSizeMB=(number in MB)
Decreases shared memory so private memory can increase

Not always needed, especially not on AIX boxes

11
Network Optimization
Use the fastest NICs available
Use multiple LAN segments to isolate network traffic, at the high-
end user loads
Specifically
S ifi ll ffor clusters,
l t a private
i t LAN segmentt for
f intra-cluster
i t l t
network traffic is strongly recommended

Consider using a secondary NIC for cluster traffic

This also provides redundancy if the secondary NIC for
private LAN traffic fails,, the cluster traffic can be rerouted to the
p
main LAN

Use DDM operating system Network probe

To test latency and thresholds

12

What Well Cover

Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

13
Transaction Logging Tuning
Transaction logging
Records transactions in a log and then writes them to disks

f Makes writes faster

Crashed servers recover faster

f There is no need to run Fixup because there are no partially

written transactions
Your backup software needs to be:
Certified to work with transaction logging

Able to archive transaction logs as to not fill up space

Disable transaction logging on:

log.nsf and mail.box database AND template

f Advanced settings on database properties tab

14

Transaction Logging Tuning (cont.)

Transaction logs should be located on a physical drive
Dont put this on the SAN

If youre
running
i Domino
D i 8.5.1
8 5 1 Create_R85_Log=1
C t R85 L 1
Optimizes transaction log format for Domino 8.5 servers

Enables logs to use block size higher than the default size of
512 bytes
f This requires that you bring down your server, back up, and
delete existing
g transaction logs
g before recreating
g them
DANGER WILL ROBINSON!

15
Indexer Tuning
Your directory is the brain of your Domino server
If its not properly optimized, ACL and view look-ups, client
sessions, and everything else will be slow
Mi i i customization
Minimize t i ti
Particularly to the number of custom views that have to be
maintained
Set the view rebuild directory to something other than your data
directory
View_Rebuild_Dir=<directory
_ _ yppath>
Update_Access_Frequency=(number in days, default 7)
Reduces the frequency of updates to rarely accessed views
allowing faster updates to more frequently used views instead
f DO NOT set this too low, or below 4

16

Indexer Tuning (cont.)

Update_Note_Minimum=(number, default is 20)
Controls how many changes must exist for a view update to
occur
f Increasing
I i reduces
d th activity
the ti it off the
th Update
U d t task
t k
f Decreasing will help keep database views up to date in a
more timely fashion
Update_Idle_Time/FTUpdate_Idle_time=(number in seconds,
default is 5)
Changes
g the amount of time the indexer waits between
database operations
f Lowering this will allow the indexer to process updates more
frequently, and as a result will consume more resources

17
Indexer Tuning (cont.)
DEBUG_DISABLE_CHRONOS=1 (default is 0)
Stops the Chronos task from performing hourly updates of FTIs
set to immediate
f Only
O l dod this
thi after
ft understanding
d t di the th impact
i t
Update_Fulltext_Thread=1 (default is 0)
Allocates a separate thread to do full text indexing, so that long
full text indexes dont delay view updates
f View updating will still work in updall

18

Indexer Tuning (cont.)

Use these together
SERVER_NAME_LOOKUP_NO_UPDATE=1

f Tells the server to use the old index while the new one
catches
t h up
DEBUG_ENABLE_UPDATE_FIX=8191

f Fine tunes when the directory indexes get refreshed

DDM Directory Directory Availability probes

Monitors the availability of all directories being served by the
server and reports any errors
server,
f Includes errors with view indexes

f Also tells that the server is up

19
What Well Cover
Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

20

ODS Tuning
Domino 8.5 uses ODS 48
Use Create_R8_Databases=1

Yields significant performance improvements over previous

versions
i
Domino 8.5.1 uses ODS 51
Use Create_R85_Databases=1

Allow compression of document data or consolidation

of attachments via the Domino Attachment and Object
Service (DAOS)

Set this in the configuration document

This setting will be ignored by Domino < 8

f Also, your ODS doesnt replicate

21
ODS Tuning (cont.)
New applications and those who have the following command run
on them, get automatically upgraded to the new ODS
Load compact c

ENABLE_ON_DEMAND_COLLATIONS=1
Reduces the unnecessary server load of creating indexes for
columns that are not being used
This is done by deferring the creation of indexes until the user
first chooses to sort the view by a specific column
f Available
A ailable to applications with
ith ODS 48 or higher
DAOS
Saves up to 50% of space by consolidating attachments
Enabled via database properties Use Domino Attachment and
Object Service for transaction logged ODS 51 applications
22

ODS Tuning (cont.)

Design compression
Reduces the size of databases by compressing design
elements by up to 60%
Enabled
E bl d viai ddatabase
t b properties
ti for
f applications
li ti with
ith ODS 48
or higher
Data compression
Can provide 40% size savings

Enabled via the database property setting

Database Names List

Applications with ODS 48 or higher create a names list, which
is a master list of all the user names listed within any document
in the application
f This makes renames a lot faster and more efficient

23
Cluster Tuning
Depending on what style of clustering you use (active-passive vs.
active-active) Spread all databases evenly across your cluster
servers
Putting all mail files on one server leaves the others un-utilized
un utilized

Monitor the SAI or Server.AvailabilityIndex

Clustered servers determine their own workload

A high SAI indicates a lightly loaded server

Monitor Server.AvailabilityThreshold
The threshold at which the server will enter the
busy state and fail over
f Set config Server_Availability_Threshold = n

24

Cluster Tuning (cont.)

Monitor and adjust Cluster_Replicators
Use this setting to start multiple cluster replicator tasks

f More replicators doesnt always mean better performance

Monitor and adjust Server_MaxUsers=(number, default is

0=unlimited)
Restricts the number of active users allowed on a server

Monitor and adjust

j Server_MaxUsers=(number)
_ ( )
Maximum number of concurrent sessions, including server
sessions that are allowed on the server

25
Cluster Tuning (cont.)
As mentioned earlier, use multiple NICs and private LAN
segments for cluster traffic
Server_Clueter_Default_Port

Dont cluster over a WAN with inadequate bandwidth

Use a monitoring tool to help you with this

Use Show Stat to figure out:

How many times a server redirected a client to another cluster
member
How many times a client tried to open an out-of-service
database
How many times a server was in a busy state or unable to
redirect clients to other cluster members
26

Cluster Tuning Important Statistics

Replica.Cluster.WorkQueueDepth.xx
Number of databases are waiting in the cluster work queue to
be replicated
f High
Hi h numbers
b butb t especially
i ll high
hi h averages indicate
i di t a cluster
l t
replication problem
Check disk and network bottlenecks

Replica.Cluster.SecondsOnQueue.xx
Number of seconds replication
p events are waiting
g to replicate
p
with other cluster members
f High numbers but especially high averages indicate a cluster
replication problem
Check disk, memory, and CPU bottlenecks

27
Cluster Performance Tuning Cluster Analysis Tool
Will help you find issues with your cluster environment
Decommission Server Tool does something similar if youre
just looking to verify if you have a matching set of applications

Run from the admin client

Server Tab Analysis
Cluster Analysis
f Creates cluster analysis
database on local

28

Working with Server Tasks

Turn off and disable unused tasks
This seems obvious, but its not

This is a HUGE security risk as well

Odds are if you inherited your environment, there are tasks

running you dont need
f Use the admin client to tell you whats running

29
Working with Server Tasks (cont.)
Dont schedule archiving, domain indexing, or maintenance
during production hours
More on maintenance next

D t schedule
Dont h d l domain
d i indexing
i d i during
d i peakk hours
h
Reduce logging when possible
For example, with Converter_Log_level=10

f Gets rid of those Begin CD to MIME Conversion (Process:

Router <message number>. messages)

30

Tuning Routing
Minimize the number of mail rules used by the server
Use journaling only when necessary

f All this slows down mail routing

Implement quotas and archiving

To reduce the overall size of applications

Use DDM Default Messaging/Mail Flow Statistic Check probe

Measures standard statistics Includes mail waiting check

Use DDM Default Messaging/NRPC Routing Status probe

Verifies that mail is routing internally

31
Turn Off and Disable All Unused Ports
Again, seems obvious but

32

Working with Server Protocols

Compress all TCP/IP traffic on all servers and clients
To gain up to 40% faster speed of communication

Avoid
A id encrypting
ti TCP/IP traffic
t ffi unless
l necessary
It adds up to 20% to the existing response time

Use IP protocols on all servers

This isnt much of an issue anymore but there still are duplicate
or conflicting
gpports out there

33
What Well Cover
Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

34

What Causes Corruption?

Lots of changes to a database
The more changes to a database, the greater your chance for
corruption
F
Frequent t view
i and d Full
F ll T
Textt Index
I d (FTI) refreshing
f hi or rebuilding
b ildi
Consider a 20 Gig mail file with FTI update frequency of
immediate
Insufficient hard drive space
Third-party apps improperly set up to lock open DBs
Partially written transactions or changes
Agents running against non-existent views
Running defrag on the OS with Domino running

35
How Do I Find Corruption?
Ad hoc Your phone rings/you get a ticket
Corruption can cause lack of access to applications

Corruption may cause phantom data to appear in a view

Corruption may generate an error message for end users

Domino server log or notification on keywords such as:

corrupt, RRV-bucket, b-tree

DDM Default Database/Error Monitoring probe

Reports
R t errors on allll databases
d t b
f Including key databases

f Find corruption before its noticed!

36

The 3 1/2 Commands That Fix Most Issues

Update
AKA Indexer is loaded at server startup by default

Runs continually and rebuilds view indexes

Updall
Evoked on an as needed or scheduled basis

While views are being rebuilt, users are locked out of

that view
Can create/update/fix corrupted view indexes or Full Text
Indexes
Purges deletion stubs from DBs and discards view indexes

Runs by default at 2 a.m. on your servers

f More on why you may not want this setting later

37
The 3 1/2 Commands That Fix Most Issues (cont.)
Compact
Upgrades the On-Disk Structure (ODS) of a database

Used to regain disk space

f But it also makes databases more efficient

f It can also clear up corruption

Removes documents from a database if archiving to a server is

set up via policies
Comes in three styles

f In-place
In place with space recovery
f In-place with space recovery and reduction in file size

f Copy-style compacting

38

The 3 1/2 Commands Compact Styles

In-place with space recovery
Retains Database Instance ID (DBIID)

f Important for transaction logging

The database can be accessed while this runs

Default if no switch is used

f This is the same as compact b

In-place with space recovery and reduction in file size

Assigns
g a new DBIID
f Only appropriate for transaction logged servers if
incremental differential backup software is used
Also known as compact B

More resource-intensive and slower than compact

39
 The 3 1/2 Commands Compact Styles (cont.)
Copy-style compacting
Meaning compact c

Makes a complete copy of the database

f It does the same thing as File Database New Copy

f Then it deletes the original

Requires sufficient disk space

Assigns new DBIID

Does not allow access to the DB while this runs

f DB access can b be granted

t d by
b adding
ddi ththe L
L
f But if DB changes, compact is cancelled

Use as needed to repair corruption

40

The 3 1/2 Commands That Fix Most Issues

Fixup
Resolves inconsistencies resulting from partially written operations,
including improperly closed databases
f Not needed when you use transaction logging

Runs automatically as a multi-threaded task at startup

f By default Domino uses # processors x 2

Verifies every item in a database, including data, design notes, and

view indexes
f If the item is found to be inconsistent, then it is DELETED from db

Takes open databases offline for duration of task

f This database cannot be opened because a consistency check of

it is in progress
Tells updall what to work on

f If a view is found to be inconsistent, they are marked

41
Updall Switches
Updall R
Rebuilds all used views, no matter how long ago they
were used, including corrupt ones
Processor-intensive
P i t i and d runs serially,
i ll one database
d t b att a time
ti
f Youll probably need to use indirect files to allow you to run
multiple instances of this
Schedule this carefully

f And make sure it finishes during off hours

Updall database.nsf
database nsf T
T $Servers
Updates a specific view

42

Compact Switches
Compact S 15
Compacts DBs with 15% or more unused space

Compact R
Compacts without conversion to current Domino release

Uses copy-style

Compact D
Discards built view indexes and runs a copy-style compact

Compact a
Archives
A hi and
d deletes
d l t documents,
d t then
th compacts t DB
f For more compact switches, see Administrator Help

43
Fixup Switches
Fixup L
Logs every database that Fixup opens and checks

f Without this, only encountered problems are logged

Fixup C
It only checks the data and reports back, but does not purge
corrupted documents
f If you need to show yourself that Fixup isnt needed, maybe
tryy using
g this

Fixup F
Checks all documents in the database

44

How Do I Fix Corruption?

Ad hoc on the server console or Files tab in the admin client after
finding out
See the 3 1/2 commands that fix most issues

Can
C beb run against
i t entire
ti server, specific
ifi databases,
d t b allll
databases within a folder

Scheduled Program documents

Automated Using
g Domino Domain Monitoring
g ((DDM))

45
Best Practice Maintenance
Transaction logging
Compact b

Updall R X

f Or create a new replica if used for corruption resolution

No transaction logging
Fixup F L

Updall R X

Compact B

f Or create a new replica if used for corruption resolution

46

Best Practice Maintenance (cont.)

Implement transaction logging
And eliminate the need for Fixup

Do not use compact, Fixup, or updall on all databases during

production
d ti hoursh
Tasks are very resource-intensive and will impact response

Use one task at a time

Allowing these tasks to run over each other may cause
corruption
f We
Wellll discuss a common issue that you too may be having
with this shortly (Hint: ServerTasksAt2=)

47
How to Execute Database Maintenance
From the Domino server console in your admin client
Load compact mail\ftanner.nsf c

From the Files tab, right-click on the database

48

How to Execute Database Maintenance (cont.)

From a Program document
Program name is the task you want to run

The Command Line field holds the options

49
Automating Maintenance
Note that nearly all of this maintenance and monitoring can be
automated easily in Domino 7 and later
Use Program documents to schedule compact task

f Use
U indirect
i di t files
fil tot speedd it up
Use OS scheduling to automate tasks that require the server to
be down
Use DDM to automate the Review items

Use DDM to run tasks, such as compact and Fixup, on an

as-needed basis

50

Automating Maintenance (cont.)

If you want to execute multiple server commands, put them in a
text file and reference them from the Program document
Program name: nserver

Command
C d liline: c < C
C:\lotus\domino\data\maint.txt
\l t \d i \d t \ i t t t
f Be careful, they are all submitted at the same time

It does them concurrently, not sequentially

51
Using Indirect Files to Automate Maintenance
If compact is taking too long, try breaking the list up into smaller
pieces
IND files or indirect files were introduced in ND6
An
A iindirect
di t file
fil is
i a ttextt fil
file th
thatt lists
li t ddatabase
t b file
fil names or
directory names
f You can use them with the compact, updall, or Fixup task on
the Domino console command line
The indirect file allows you to specify more than one
database on the command line

52

How to Create and Use Indirect Files

Create IND files using a text editor
List the names of the files to affect

Include the subdirectory with the file name, if it has one

f To do an entire subdirectory, enter only the name of the

subdirectory
Save the file with an IND extension

Use them with the maintenance commands

Compact B mail1.ind

Updall RR system.ind
system ind

53
Run Indirect Files Using a Program Doc
Combine the methods to run your maintenance routines
Create an IND file that contains the path and file names you
want to run maintenance on
Create
C t a TXT fil file containing
t i i ththe commandsd you wishi h to
t run
Create a Program document to tie it all together

f Its the best approach with the most control!

54

Example Using Windows OS

Use the scheduler or AT commands to schedule this monthly task
on each server
Here is an example of a CMD file you could use:

f Files.ind
Fil i d contains
t i theth files
fil youll
ll maintain
i t i
f Offlinemaint.cmd is the command file you schedule

It shuts down the server, then runs all the maintenance offline

f Then it restarts the server when all tasks have run

55
Best Practice Maintenance
Avoid conflicting/overlapping maintenance commands
It will cause corruption

Remove S
R ServerTasksAt2
T k At2 ffrom your Notes.ini
N t i i
Most admins dont know its there and schedule compact or
other conflicting server tasks at 2 a.m., causing corruption
Avoid editing the Notes.ini directly via the operating system

f Doing so is impossible to track and troubleshoot in case of

issues

56

What Well Cover

Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

57
Domino Configuration Tuner
Runs on your client and analyzes server documents, tasks,
Notes.ini, database properties of one or many servers
Download it here:
www 01 ibm com/support/docview wss?uid=swg24019358
www-01.ibm.com/support/docview.wss?uid=swg24019358
After initializing the server list for the first time, the scan will run
in the background
Watch your status bar for completion

58

Domino Configuration Tuner (cont.)

59
Domino Configuration Tuner (cont.)
Be sure to check out the Links and References section
Check for updates from time to time
Turn off unwanted rules under Preferences

60

Server Statistics
Weve talked about several statistics to monitor
Admin client Server Statistics shows them in a
categorized way to make them easy to access

61
Disk Statistics to Watch
Disk stats are the number one problem on slow performing
servers

Diskk stats
Di t t are collected
ll t d in
i different
diff t ways, but
b t allll off them
th have
h
PctUtil as part of the stat
It could be Logical Disk or Physical Disk

Like Platform.LogicalDisk.1.PctUtil.Avg

f This should rarely hit 60% on Wintel boxes

Watch out Disk 1 isnt

isn t necessarily your \data directory
f On AIX and iSeries, it really depends on how the disk
sub-systems are configured
They often can run 90% without issues

62

Disk Statistics to Watch (cont.)

Platform.LogicalDisk.1.AvgQueueLen
Average number of read and write requests awaiting service on
the logical disk
f You
Y can hit high
hi h peaks
k occasionally
i ll without
ith t iissues
Queues of more than a couple of seconds mean your disks
cant really keep up with the action
f A constantly high number means moving users or apps

Balance these disk stats against CPU/memory stats

Because memory = virtual disk

f And constant thrashing of disks might mean you need more

RAM

63
Putting DDM to Work for You
Use any applicable DDM probe to help you understand server
short comings

64

Dont Forget About Events Handlers and Generators

They can still proactively inform you
of database, server, routing, statistics
tasks, and other server issues
Some event handlers are set up by
default
But theyre not nearly sufficient

No event generators are turned on

by default
So youll never know about issues

65
Activity Logging and Activity Trends
Enabled via the Configuration Settings document Activity
Logging tab
Records user activity by person, database, and access protocol

Can
C be b summarized,
i d averaged,d or trended
t d d over time
ti to
t measure
and compare workloads across servers
Can be used in conjunction with the Domino Change Manager
to automate the creation and execution of workload
redistribution plans to load a new server, decommission an old
one, or balance workloads across unevenly burdened servers
Activity logging is categorized under Monitoring/Managing
Servers
f Activity Trends is categorized under Performance

66

What Well Cover

Introduction
Tuning your hardware, OS, disks, and network
Domino transaction logging and indexer tuning
Working with your ODS, clusters, tasks, and ports
Preventing corruption and maintaining your data
Working with DTC, DDM, statistics, and activity trends
Wrap-up

67
Resources
Lotus Domino Domain Monitoring Redpaper
www.redbooks.ibm.com/abstracts/redp4089.html

Domino 7 Performance Tuning Best Practices to Get the Most Out

off Your
Y Domino
D i Infrastructure
I f t t
www.redbooks.ibm.com/abstracts/redp4182.html

Introduction to Domino performance tuning

www.ibm.com/developerworks/lotus/library/ls-perf_intro/

68

Resources (cont.)
Notes.ini analyzer and reference by entry
www.lntoolbox.com/en/notesini-reference.html

Domino Tuner Blog

www.bleedyellow.com/blogs/DCT/?lang=en_us

Lotus Notes and Domino wiki

www-10.lotus.com/ldd/dominowiki.nsf/dx/activity-logging-and-
activity-trends
New default limit on UBM size in Domino 8
www-01 ibm com/support/docview wss?rs=0&uid=swg21268988
www-01.ibm.com/support/docview.wss?rs=0&uid=swg21268988
Best Practices for running Lotus Domino in a SAN
www-01.ibm.com/support/docview.wss?uid=swg27002613&aid=1

69
7 Key Points to Take Home
When dealing with performance problems, dont just address the
data OR the hardware OR Domino
Only adjust settings after identifying a problem, testing, and
measuring their impact
Use automated tools to maintain your data and prevent corruption
Use DTC to quickly understand what can be improved
Implement transaction logging to minimize disk writes and
corruption due to impartially written transactions
Keepp current with application
pp ODS and server versions as theyy
provide many performance improvements
Use DDM, statistics, cluster analyzer, and activity logging to help
you understand whats happening on your server

70

Your Turn!

How to contact me:

Francie Tanner
Francie.tanner@panagenda.com
71


Wellesley Information Services, 20 Carematrix Drive, Dedham, MA 02026

Copyright 2011 Wellesley Information Services. All rights reserved.