The following are some tips for making applications/views that perform well even with reader access controlled documents:
- Embedded view using Show Single Category. This is the winner, hands down. If your data is structured so that users can see all the documents in a category, then you can display just the contents of that category very quickly to the user. In some cases, it may make sense to let the user switch categories, in which case you have to consider whether or not he can see the contents of the other categories. But in most cases, the view would be something like My Sales and would show all the sales documents for the current user. The caveat for this kind of view is that the user interface for the Notes client is not quite as nice as the native view display. For Web browsers, it is just as good, and we have never seen a reason not to use this kind of view for Web browser applications. In fact, the performance is so good that it’s faster to open one of these with reader access controlled documents than to open a native view without reader access controlled documents!
Read more…
Viewed 10417 times by 2515 viewers
Here are some tips about view performance, regardless of whether or not reader access controlled documents are present.
Time/date formulas
Using @Now or @Today in a column or selection formula forces a view rebuild every time the view is refreshed. Therefore, if you use this kind of formula, consider making the view refresh Manually or “Auto, at most every n hours.” That way, when users open the view, they will not have to wait for a view rebuild (or rarely so, in the latter case). The downside to this is that the view may be out-of-date because it opened without trying to refresh. Consider the contents of these views and how fast they change to determine whether or not you can use these indexing options safely.
Read more…
Viewed 8738 times by 2603 viewers
We have seen a dramatic increase in the number of critical situations related to Lotus Notes Reader Names fields and Lotus Notes views. Customers find that performance is unacceptable frequently throughout the day. They cannot understand why because the code reviews and pilot tests all went smoothly. But a few months after roll out to their entire department/division/company, they find that complaints about performance are dominating conversations with their employees, and something has to be done.
Read more…
Viewed 4422 times by 1308 viewers
The first thing in lotus notes view you should know before troubleshooting a performance in notes view problem involving. Lotus notes server may indexing for indexing is how the process works. Indexing is usually done by the task of updating, which runs every 15 minutes on the Domino server. Technically, it is possible to adjust the interval, but it is to rename files, so it is rarely done.
When the Update task in Domino Server runs, it looks for each notes database on the Domino server with a modified date newer than the last time the task ran Update. So the task updates the views in those databases. Based on our experience, it is reasonable to assume that it takes about 100 milliseconds to update a display in a normal production database in a production environment.
Read more…
Viewed 5751 times by 1511 viewers
Don’t maintain unread marks.
If check this option in database properties, unread marks will not be tracked in your application regardless of the settings you have for each view. I’m used to track the time client_clock enabled database and I can see that I was surprised. For large application (about 20 GB with 200,000 documents), my Notes client could open the database in about five seconds without unread marks, including network traffic. With unread marks turned on, I had to wait an additional six seconds or more. This additional time was spent in GET_UNREAD_NOTE_TABLE and RCV_UNREAD. With unread marks turned off, these calls aren’t made.
Read more…
Viewed 8558 times by 2034 viewers
