Hi!
I have to solve a performance problem and I need your assistance please!!!
There is one database with a really big number of documents and a big number of views. The users complain that it takes them time to access this database.
One attempt of solving this issue was to create a new copy of it. At the begining it was just fine, but after 15-20 days the performance started to decline again. Can anyone explain me why it behaves like this and how can I solve this problem?
This is not about deletion stubs, because we have the proper setting on the database properties and reducing the number of the views is out of question.
Thanking you in advance.
Subject: Database performance & new copy effectiveness
Hi,
U can check diffrent things:-
-
Monitor the console of Domino server is there is any view is Corrupted, if there please refresh the view.
-
Check the %used of database, should be more than 90%, if not run compact.
-
Schedule Updall with -R,
-
Run Fixup with -R.
Regards
Jai
Subject: RE: Database performance & new copy effectiveness
I would say read -undread marks.
JYR
Subject: RE: Database performance & new copy effectiveness
The issue sounds a lot like there are a bunch of views and your making a new copy got rid of all of them now they are back up to size and performance goes into the tank. A number of years ago I was called in on a consulting assignment to see why a database that was working reasonably well was now painfully slow. The first thing that I found was that there were way to many views in it, I can’t remember the number but it was over 100 and if my memory is correct it was close to 200. So the first thing we did was add a little action to the View QueryOpen that created a document and sent it to a mail-in DB. The document contained the view name, the user name and the date and time. I was then able in the mail-in DB to create some views that I used to evaluate what views were being used and by whom. After a little investigation I was able to eliminate almost 50 of the views as no longer being of any importance be cause they were never accessed (careful here because views that were only used by agents are not recorded by this method) Next I found that another big wack (that is a scientific term meaning I can’t remember how many) simly variations of another view. I consolidated several of these into a single view by adding sortable columns. The next group was a series of views that were identical except they had a slightly different view selection formula (as I remember there were abot 10 of these) that gave views where the status of the document was different. So there was one for Status = “New” another for Status = “Recieved” etc. I built one view that was categorized by Status then incorporated into as Single Category Views on different Pages that the user called from a navigator menu.
The net result was to reduce the total number of views from upward of 200 to somewhere in the 20 - 30 range. One of the strengths of Notes is how easy it is to build views, it can also be a serious performance issue.
Oh! one other place to look is for Personal Views.
Hope this helps! I would guess from your description that it is an issue with the views. I also like to periodically (particularly with a new DB before it goes into product) create a New Copy and use it as this cleans up a lot of junk that can build up especially during the development process. Careful though if a database is replicated because you will have to do a new replica of the New Copy everywhere it is used.
Subject: Database performance & new copy effectiveness
Thanks for all your responses.
We compact the database every weekend and we run updall and fixup every night.
Raphael you are right, but I was desperated.
JYR, the property “Don’t maintain unread marks” is unselected, although it should be enabled to improve performance. The reason I do not selecting it,is because I have a “Go To” button from another database, that opens a categorised view in this database, collapse all categories apart from the required one and when “Don’t maintain unread marks” property is selected the collapse/expand property of the view does not work at all. Do you know why?
Bill your idea is very clever. I will suggest that to the client.
Maria
Subject: Database performance & new copy effectiveness
I know this is a day late, but do not make a copy of a db in order to solve performance problems !
When you make a copy, you eliminate all your views, so view indexing is temporarily improved. But as users use these views, they have to take the hit for indexing, and then of course the server will maintain those indexes just as it did before. So no gain there.
As well, you will clean out deletion stubs and the field name table, but these are probably not your issue.
Please do read those performance articles. I’m happy to talk with you more about performance if you’re still unsure after reading them.
regards,
raphael