Maybe a stupid question, but:
Is there a rule for how many data there is transfered from the server to the client when opening a 25 Gb db with approx 25K documents.
We’re facing some performance problems with our environments. ( 6.5.1 on Win 2003, data dir on Netapp storage with iscsi connection )
Subject: RE: Data transfer
25,000 is not a lot of documents, and under normal circumstances should not present a performance challenge, even when the individual documents are large. When you talk about opening a database, that can mean a lot of different things, but generally we’re talking about opening a frameset, view and page with outline, and the view is potentially the slowest of these.Generally, if there is a delay it’s not due to network I/O, but to work occurring on the server to update the view index or to decide which documents the user has access to view. The main factors that affect this are:
design of the view: Are there formulas that use @Today or @Now, or that are excessively long/hard to compute? Does the view categorize documents multiple ways, so that there are many more view rows than there are documents?
number of modifications: Opening a view requires checking for document updates since the view was last used, to see whether any of the modified documents should be added/removed. If there are a lot of these, it takes longer.
whether Reader fields are being used and if so, what percentage of the documents the user has access to (fewer takes longer).
The server doesn’t send the entire view contents to the client at one go – only enough to fill a screen.
See IBM Redbooks Performance Considerations for Domino Applications for some hints.