Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Maximum size of NSF file
- Thread starter maqsa
- Start date
In R4 the max size was theoretically 4GB. Since R5, there is no technical limitation to the size of a Notes database - it can grow as large as the disk space allows.
As far as performance is concerned, I would be wary of dealing with a 12GB database on a machine that is not performant. Nobody will pretend that Notes is not a demanding application, and the bigger the database, the worse things tend to get unless the design is very basic.
Personally I have worked with databases containing over 150,000 documents without any issues, but the PC was a rather powerful one (recent CPU, 2GB of RAM, 7200RPM 120GB discs).
Your mileage will vary function of the performance of the PC in CPU horsepower, amount of RAM and speed of HDDs, but also function of the number of documents in the database, the number of views and the amount of calculated info in said views.
Actually, the view design is almost the primary criteria in the end. If the columns have a lot of info that needs to be calculated, the view will be slow even for 100 documents. If the view only shows info that is already calculated on the documents it contains, then it will be the number of documents and the power of the PC that will define the performance.
Finally, if the server is not powerful enough to respond quickly to average use, then it will struggle to index and display a document-heavy view.
In the end, it is quite difficult to give a performance forecast in Notes. Personally, I have talked with Lotus employees and managers at LotusSphere, and I've never been able to get an answer any more firm than what I've just said. Actually, Lotus still doesn't give out clear field sizes and document structure that would allow to estimate the size evolution of a Notes database.
I find that quite frustrating.
Pascal.
I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
As far as performance is concerned, I would be wary of dealing with a 12GB database on a machine that is not performant. Nobody will pretend that Notes is not a demanding application, and the bigger the database, the worse things tend to get unless the design is very basic.
Personally I have worked with databases containing over 150,000 documents without any issues, but the PC was a rather powerful one (recent CPU, 2GB of RAM, 7200RPM 120GB discs).
Your mileage will vary function of the performance of the PC in CPU horsepower, amount of RAM and speed of HDDs, but also function of the number of documents in the database, the number of views and the amount of calculated info in said views.
Actually, the view design is almost the primary criteria in the end. If the columns have a lot of info that needs to be calculated, the view will be slow even for 100 documents. If the view only shows info that is already calculated on the documents it contains, then it will be the number of documents and the power of the PC that will define the performance.
Finally, if the server is not powerful enough to respond quickly to average use, then it will struggle to index and display a document-heavy view.
In the end, it is quite difficult to give a performance forecast in Notes. Personally, I have talked with Lotus employees and managers at LotusSphere, and I've never been able to get an answer any more firm than what I've just said. Actually, Lotus still doesn't give out clear field sizes and document structure that would allow to estimate the size evolution of a Notes database.
I find that quite frustrating.
Pascal.
I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
- Status
Similar threads
- Locked
- Question
- Locked
- Helpful tip