jimm123
asked on
Notes Application Latency
I have 3 offices - 1 in India, 1 in Chicago, 1 in Germany
A notes application sits on a Domino server in Germany. Clients in India and Chicago access the same database.
For the Chicago clients they are able to open and view documents in the application in a few seconds. For the Indian users accessing the same data takes a few minutes.
Both India and Chicago are using a 1mb T1 internet line.
What could be the cause of such latency?
madheeswar
Did u checked PC configurations?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
An Update
The notes database is accessed using both the web interface and Notes client.
What I have found is that as the file size of a document increases the longer it takes to open the document using the Notes client. For example, on a p3 880 w2k ws with 128 ram a document 20mb in size took almost 10 minutes to open.
However, the same document accessed throught the web client took only a couple of seconds to open.
What would cause such a difference. FYI - the results were the same for all office locations.
The notes database is accessed using both the web interface and Notes client.
What I have found is that as the file size of a document increases the longer it takes to open the document using the Notes client. For example, on a p3 880 w2k ws with 128 ram a document 20mb in size took almost 10 minutes to open.
However, the same document accessed throught the web client took only a couple of seconds to open.
What would cause such a difference. FYI - the results were the same for all office locations.
Well one thing that you should understand here... you are comparing apples and oranges
When you open a document in notes all the calculations/lookup/open scripts/formulas are all run from local clients memory and processor, but when it is web the server (which is more powerful than client) does all the above tasks and converts into HTML and sends it out to the browser and browser just displays the data..wherein not much processor or memory used as it used in notes.
Hope that clarifys things... what we can do is to architect the form efficiently so that for eg, if you have someone embedding large attachments into the richtext field, just move the attachment to seperate document and provide a link to it using notes:// protocol or some button script to do a lookup in the files view where attachments are stored and retrieve them as needed
When you open a document in notes all the calculations/lookup/open scripts/formulas are all run from local clients memory and processor, but when it is web the server (which is more powerful than client) does all the above tasks and converts into HTML and sends it out to the browser and browser just displays the data..wherein not much processor or memory used as it used in notes.
Hope that clarifys things... what we can do is to architect the form efficiently so that for eg, if you have someone embedding large attachments into the richtext field, just move the attachment to seperate document and provide a link to it using notes:// protocol or some button script to do a lookup in the files view where attachments are stored and retrieve them as needed
Hemantha,
You may actually have it backward on the calulation equation. A fast Domino server under load is actually slower than a slow Notes workstation that isn't doing anything other than openining a single document.
Imagine I have 50 users on one Domino server. The typical document on that server requires, say 500ms of calculations for a client, or 25ms for the server (using a web browser). That makes the server 20x faster than the workstations.
If one client opens one document with no other load on the server, that takes 500ms (ignoring network latency). Using a browser? 25ms.
Two clients simultaneosly -- stil 500ms, as they calculate concurrently. (Still ignoring latency, but now also ignoring the I/O sequening on the server.) The server now takes 50ms instead of 25ms.
10 clients -- 500ms is still the rule. 10 browsers -- 250ms.
20 clients -- 500ms. 20 web browsers -- 500ms.
50 clients -- 500ms. 50 web browsers -- 1250ms.
You may actually have it backward on the calulation equation. A fast Domino server under load is actually slower than a slow Notes workstation that isn't doing anything other than openining a single document.
Imagine I have 50 users on one Domino server. The typical document on that server requires, say 500ms of calculations for a client, or 25ms for the server (using a web browser). That makes the server 20x faster than the workstations.
If one client opens one document with no other load on the server, that takes 500ms (ignoring network latency). Using a browser? 25ms.
Two clients simultaneosly -- stil 500ms, as they calculate concurrently. (Still ignoring latency, but now also ignoring the I/O sequening on the server.) The server now takes 50ms instead of 25ms.
10 clients -- 500ms is still the rule. 10 browsers -- 250ms.
20 clients -- 500ms. 20 web browsers -- 500ms.
50 clients -- 500ms. 50 web browsers -- 1250ms.
In a complex application, the web browser often wins out in network transport. If 20% of my data fields are hidden on teh form, then 20% of the data never trasnfers. And teh form, untl it is cached on the client, usually takes less data to describe an instance in HTML than the size of teh form's binary data itself.