Why bother with performance. Well it lowers
the costs of ownership and make the end users a lot happier.

Monitoring Performance. This is best
done from the end users point of view, check your helpdesk call logs and
see what calls are coming in from users in relation to performance. It
is also good to keep and eye in the availability index stats that shows
how long it is taking to perform transactions. Obviously both DDM and Activity
Trends can also be used to measure performance.

Server sizing that is based on peak
times can mean that resources can go unused at off-peak times.  This
means you can schedule some other tasks for these times thus saving resources
and allowing more users on the server without the need for new hardware.
Some of these may be like the scheduled replication or the Indexer task.

The indexer task runs all the time.
In Domino 7 your can disable the indexer task using the UPDATE_Disable_Views=1
but the views are still updated when a user opens the database but for
mailfiles this may not be handy as users always leave their mailfiles open.
 You can schedule a view update using UPDALL.  Some more ini
parameters are

Update_Access_Frequencies=n ( default
7 )

Update_Note_Minimum=nb ( default 7 )

Update_Idle_Time=n ( Default 5 )

You can also increase performance by
tweaking the Full Text index by looking at the database properties. Now
if you wanted to disable all database that are set for hourly full text
updating you could change all databases or just add DEBUG_DISABLE_CHRONOS=1.
 This stops the chronos task from scheduling the hourly update task.

If you have a lot of agents on your
server you might want to look at how many threads you are using for Agent
Manager.  In DDM there is an Agent Application probe that will check
all agents to see which ones are using the most CPU time.  This is
handy for finding agents that could be scheduled for off-peak times.

If you are using domain indexing or
directory catalogues you should schedule these for off-peak hours.  Same
with server based archiving using program documents.

Reducing Resource Use

Keeping sessions open can be turned
on using the ini param MailLeaveSessionsOpen this is handy for servers
that do a lot of internal mail routing, leaving the sessions open will
lower bandwidth as handshaking between servers no longer needs to happen
for each session.

Avoid message conversion.  Keep
it in the senders format.

Mail rules.  The rules that fire
the most should be set first and use the new |Domino 7 Stop Rule Processing
feature.

Less logging. Turn off debug parameters
when not working with Lotus Support, lower or turn off logging to the console
whenre you can as it can be fairly resource intensive.  just keep
the logs your need.  If there is a problem you can always turn them
up when tracing the issue.

keep your databases in cache longer.
set NSF_DBCache_Max_Clean_Hold_Time=9999 so that opens are faster.this
isd handy for leveling out peaks when users are opening a lot of different
databases at the same time like just after lunch.

Server Consolidation

By moving users to fewer server you
have fewer servers to m onitor, upgrade, maintain, less replication traffic
on network and probably less email traffic as there is a higher chance
that the user you are sending to may be local. but a server failure will
effect more users ( unless you cluster ).One point of warning is that Domino
defaults are designed for moderate user loads, when you add more users
you may start hittings limits you have never encountered before like virtual
address space running out.

NRPC Max concurrent transactions is
20 is a multi processor server you should increate this with Server_Max_Concurrent_trans=n.
 

Multiple mail.box’s is another way of
reducing a bottleneck when your server has a lot of users.

PercentSysAvailResources=n% will tell
the server to reduce the amount of virtual memory the server thinks it
has, this is handy for partitioned servers so that no one server takes
up all the virtual memory but it can also be used on single partition servers
to help leave virtual memory for other non-domino tasks.

Reduce the Net Buffer size.  it’s
the 4th parameter in the TCPIP= ini variable.

New console command ‘Show Monitors’
will show how many agent monitors are running, these can take up virtual
memory space. Mail Rules are an example of monitors.  You can also
cap the number of mail rules per database using MailMaxFilters=n

RM_No_Log_Objects_In_Mailbox=1 will
turn off transaction logging just for the mail.box files.  this can
increase performance when large emails are being sent but it does mean
is a server goes down during the routing os a large email then it won’t
be in the transaction log for recovery.,

Database utilities ( like fixup, updall
etc ) on a server with a lot of databases may not finish in one night.
You can use program docs to scheule these tasks on different nights or
use indirect files to run the tasks on a set of databases per night.

The best way to reduce load and increase
performance is upgrade to Domino 7.

…The Cleanest, Slickest Sites In Town.

Presented By Scott "The Turtle"
Wenzel.

LIVE BLOG

What is AJAX it stands for Asynchronous
Javascript And XML. It’s not a product you can buy
but a methodology in web programming. The best way to describe it is why
update a full webpage when you can just update the object on the webpage
that you are changing.  A great example of this would be Google Maps
or gMail.

How does it work. Well in IE5 MS added
a request type called XMLHttpRequest which has now been added to most major
web browswers like FireFox etc. This request can allow Javascript to pull
back XML content so you can then change the Document Object Model with
this data.  Domino is a great backend for this XML as you can design
your views etc to output the correct data. Think lookup views that output
xml.

The InnerHTML property of any DIV can
be used to contain the new data that has been retreived from the server.

Scott has just shown a very funny demo
of a webpage that needs to reload every time you click on an option and
then moved onto Google Maps where he is showing the code that runs it.
 It’s got lots of JavaScript but it only needs to load it up once.
If you want to try figure it out yourself then do a search of the code
for XMLHttprequest to find the main part.

So why not just load all the data at
once. Well as an example Scott mentioned that if you had to download all
the Starbucks locations around the world then you would be waiting for
ages but by using AJAX you just have to download the main form and then
pull the data you need using AJAX based on the selections of the user (
like Country, State, Town etc ).

One thing to note is that it is NOT
cross domain, you cannot get the XMLHttpRequest on server xyz.com to pull
data from qwerty.com

Basic uses of AJX can be things like
context sensitive help ( onmouseover could trigger the request to grab
the data ). Instructional systems that can guide users through a form or
site, populating options arrays without reloading pages, The ObjectGraph
Disctionary is a great example
of what is known as a Word Wheel that pulls in data as you type.

Possible Pitfalls

Well the first thing you notice is that
the ‘Back’ button breaks. Clicking on the back button ( or refresh ) won’t
remember your options.

You need tto check your Status Code.
You can’t use the data if it doesn’t get back to the browser. So always
wait till you get a status code ( 200 – successk, 404 – not found )

And don’t overdo it.  it’s easy
to make your site look like a circus.

LIVE BLOG

This session is going to cover the future
of the Domino roadmap.  Starting with some highlights of Domino 7
an important message is that many vendors have already released tools that
work with ND7 so there are very few reason not to upgrade while there are
loads of reasons to upgrade like a improved TCO, better performance, easier
administration with DDM, better policies and Activity Trends.

Coming Soon : Smart Upgrade ‘Run
As Admin’ install utility. This can repackage the install kit so that it
can run on any computer even if the user does not have admin privilages.

7.0.1 is due in Feb. One new feature
is that Max mailfile size enforment at router which can prevent delivery
of mail to large mailfile.

Domino Next :

Support for Hannover client

World class portal-based user experience

Extent Domino leadership in messaging
& collaboration.

Smart Upgrade will support moving client
to Hannover

Domino server will include the Hannover
client provisioning server

Extended polices to support Hannover
and workplace capabilities.

Support for provisioning composit apps
from domino

Support for Domain keys to help reduce
Spam.

Direct support for MS-TNEF

Improved support for Mime/html emails.

SpamGuru will be included.  Users
can classify mails as spam and the server will rank incoming emails to
see if they should be deleted, moved to JunkMail or just deliver as normal.

Mail recall will now be part of the
product with policies that can specify how old messages can be or if read
messages can be recalled.

New version of DDM. more automation.

Broader exposure admin API’s,

AdminP can rename/delete users up to
50 times fast

AdminP can update users client side
bookmarks if you move a database on the server ( using the admin client
)

Support for snapshot backups.

Development

simplified RSS and Atom feed generation

MIME and HTMl api’s

Unread Mark API’s

More DXL work.

More APIs – mail, calendar etc.

ability to call web services from domino
apps.

Domino 7.0.2 will support running on
Windows 64bit OS. Domino Next will fully support 64bit OS’s while the 32bit
platforms will still be fully supported ( unlike the next version of Exchange
)