Opening a database using the webbrowser can take 10 or more seconds after the login screen. This is applicable for the first user in the morning or when the server did not receive http requests for a certain time (couple of hours).
When the user switches to an other database, it also takes 10 or more seconds before it is opened.
Remarkable part is that when one user has accessed a database, an other user can open the database within a short time (1 second or less).
It looks like that something is cached for a certain time and when the database is not used for a certain time (or after server restart) the cache for that specific database is emptied. When a user is accessing the database, the cache is filled again.
Are there any ideas how to reduce the start time of the databases?
Subject: Are you using XPages?
I’ve noticed a delay on opening databases in XPages. Not always, just the first time in after a while. Are you using XPages via the web or traditional Domino web apps?
I don’t think this has much to do with view indexing as Evan suggests, at least from what I’ve seen since my databases are being developed and have no real documents yet.
I get the delay… then it’s fine for a while and eventually the delay will come back. Maybe when the browser is closed and re-opened. I’m not sure. I haven’t really tested and dug into the delay yet, but it is annoying.
Subject: Yes it is using Xpages
Yes it is using Xpages.
Subject: …ServerTasksAt2 ?
It sounds like the ‘notes.ini’ of the Domino Server is missing the following line:
ServerTasksAt2=Updall
See the topic titled, “Indexer tasks: Update and Updall” in the Lotus Administrator’s Help Database for more information.
Subject: Updall
The notes.ini has “ServerTasksAt2=UpdAll”
Probably it is related to Xpages as David Leedy is describing.