Hi there,
becasue of the rising number of users working in home office, I tried to use the Notesdatabase Property DelayUpdates but the results were not promising at all.
I have build an agent which wrote 1000 test documents into a test view on the server and afterwards deleted them again. It does this 3 times with the option DelayUpdates = true and 3 times with DelayUpdates=false.
Here is one of the results of a run (values are repeatable)
| Normal | DelayUpdates |
| 2344 ms | 2563 ms |
| 2406 ms | 2422 ms |
| 2438 ms | 2578 ms |
Has someone made better expierences with this option ? If yes, what is different to my test ?
My documents consist of:
doc.form="Performance Test"
doc.mytext=t$
doc.titel="Performance Test " & i%
Call doc.save(False,False)
t$ is a string array with 50 entries
TIA
Sincerly,
Jochen "Joe" Herrmann
Hope to make use of the Sleep ( numExpr ) statement in conjunction with DelayUpdates=false will help to add subjective delay in updating the next document from the Document collection.
Hello Pravin,
thanks for your reply, but in fact sleep would delay the process even further. With sleep I would give up processing time for other applications (not other Notes applications).
I want to find out, what exactly is the advantage of DelayUpdates and under which circumstances.
Sincerly
Jochen "Joe" Herrmann
Hi Joe,
It sounds like your server as a lot of free resources so its doing the update quicker than you were expecting. From the help we see the following: If you set DelayUpdates to True, server updates are cached and the script proceeds immediately. At a convenient time, the cached updates are posted.
It is only going to delay that update until they can be uploaded when the server has the resources.
Hello Paul,
thanks for your reply.
Well I was using for this test our developement server via VPN.
Yes, exactly because in the help was mentioned "Indicates whether updates to a server are delayed (batched) for better performance." So I tried to simulate it ...
If it would indeed delay updates by caching it, the script in the foreground shouldn't wait for the server's ok and should be indeed faster. But this is not the case in my test scenarioy. So either something is wrong in my understanding of this option or in my test code or the advantage of this option is marginal or ??
So the question now is what is this option doing ?
Sincerly
Jochen "Joe" Herrmann