Domino Tuning Parameters in notes.ini
0 commentaires
0 distinctions
0 personne(s) l'ont ajoutée à leurs favoris
database,
domino,
lotus,
notes,
number,
parameters,
performance,
redbooks,
replicator,
resources,
router,
server,
task,
tasks,
time,
tuning,
update
Domino Tuning Parameters in notes. ini Abstract There are a number of parameters in Lotus Domino s notes. ini configuration file that affect performance. This technote discusses some of them. Update June 2008: Fixed typo MaxMailThreads should be MailMaxThreads Contents Configuring server tasks Each task increases the server s load and can adversely affect its performance. Minimizing the number of server tasks that are run by the server, the frequency at which they run, and the time in which they run will enable you to increase the performance of the server. For example, these are the server task entries in notes. ini: ServerTasks=Update,Replica,Router,AMgr,AdminP,CalConn,Sched ServerTasksAt1=Catalog,Design ServerTasksAt2=UpdAll ServerTasksAt3=Object Info -Full ServerTasksAt5=Statlog Each of these variables control the schedule for automatic server and database maintenance tasks. The first SeverTasks line denotes the services that are run when Domino starts while the other lines denote the scheduled server tasks. The time is entered in a 24-hour format, where 0 is 12:00 a. m. and 23 is 11:00 p. m. In the example above, Catalog and Design tasks would initiate at 1:00 a. m. , and the Statlog task would initiate at 5:00 a. m. You can significantly improve performance by removing tasks that are not appropriate to the server. Consider the following suggestions to increase performance related to Lotus Domino server tasks. These tasks should be turned off when they are not in use: Scheduling: Turn off this task if you are not using the server for scheduling and calendaring. AMgr: Turn off this task if you are not using the server to run scheduled agents. Remember, this function is not required for WebQuery Agents. Collector, Reporter: Turn off this task if you are not using the server to automatically track server statistics on a regular basis. You can collect them on demand. Remove the Replicator (Replica) and Router tasks. Both of these tasks can be removed if they are not being used on the server, because each of these tasks take up a fair amount of server resources when loaded. For example, if you have only one Lotus Domino server in your organization that is used for both applications and mail routing, you might not need the Replicator task, because you do not have any other servers from which to replicate (and because clients will be replicating from the Lotus Domino server, not vice versa). Carefully choose the times when server tasks are run. Daily server tasks should not be run when other server tasks are running or at times when there are a lot of users using the Lotus Domino server. This allows the maximum amount of server resources to be available for each server task that is currently executing and for user sessions. Examples of such server tasks are Design, Catalog, Statlog, and customized Notes API programs that need to be run only once a day. The entries in ServerTasks have the following uses: ADMINP: The major Domino scheduler job running batch-like updates AMGR: Domino Agent Manager; takes care of predefined agents CALCONN: Connects the Domino calendar to other types of calendars EVENT: Domino Event Handler REPLICA: Domino database Replicator task REPORT: Domino Report Generator (adding data to STATREP. NSF) Page 1 of 4IBM Redbooks | Domino Tuning Parameters in notes. ini 15/08/2008http://www. redbooks. ibm. com/abstracts/tips0421. html?Open