Anyone tried , at least with 40000 documents, and time dependant columns (at least 6), and compared their performance? Which one will consume more time to refresh?
Cheerio!
Subject: How does view refresh Notes compared against Access or other databases?
This isn’t really the forum to compare Notes/Domino with something like Access (not that there is a comparison).
What do you mean “time dependent” columns? just displaying dates and times is fine, but if you’re using @now or @today or @tomorrow, etc… then you are probably going to have performance problems.
Subject: RE: How does view refresh Notes compared against Access or other databases?
Yes, @now or @today, perhaps you can guide me to the appropriate forum, just like to verify the claims from my microsoft experts and paradox users, one of them claim 50000 documents only consume around 15mb of file space,and the view is only few seconds. I would imagine if there is a faster way, surely it would have been incorporated by our Notes team in IBM?
Subject: RE: How does view refresh Notes compared against Access or other databases?
Will,
There are articles about view performance in the Developer Network pages.
Domino gives the developer an amazing amount of flexibility for coding practices, even allowing multiple languages in the front end to hit the back end API calls. If you’re sad about the performance when you try coding something one way, think about other ways to code it.
regards,
raphael
Subject: RE: How does view refresh Notes compared against Access or other databases?
Yeah, I got those articles, and trying to improve it. Just that, in my organization, we have so many Microsoft Only IT users, they keep on saying that Access will not have this problem, etc, but I have not seen any good applications being rolled out with more than 40000 documents and time dependant view (like @Now) working very fast, so just bit curious, are they telling me the truth? As I believe it the logic could have been thought, surely, our Lotus team would have incorporated them, I suspect the same problem might even appear in other applicatoins, be it Access, Paradox etc especially when you bring in lots of documents, categorization, @if formula with reference to @Now, etc.
Subject: RE: How does view refresh Notes compared against Access or other databases?
Do not use time dependent formulae in large views.Do not use time dependent formulae in large views.
Do not use time dependent formulae in large views.
Need telling again? 
If there is one way to guarantee poor performance in large views it’s using time dependent formulae. The best thing to do in order to dramatically improve performance is, er…
Do not use time dependent formulae in large views.
Frunobulax
Subject: RE: How does view refresh Notes compared against Access or other databases?
Tq, yes, I am aware about that. But I noticed there is huge performance improvement between v7 and v5, even with time dependant data, it also depends on CPU and harddisk space (from my experience). So, I guest I’ll have the same problem with other applications if it is due to time dependant data, got it… cheerio
Subject: RE: How does view refresh Notes compared against Access or other databases?
Have you thought about removing the time dependencies from your view formulae?
Frunobulax
Subject: RE: How does view refresh Notes compared against Access or other databases?
My view is a monthly reporting, it will have to show current month, year to date (ytd) and year end projection (YEP), YEP is the tricky one, which takes YTD + forecast for remaining month.
Eg: For reporting in June, it will take YTD Jan to May,forecast of June to DEc.
I have different view, which has different selection formula by region, and different sort category, if I hardcode it, it means whether I need to update design every month, or I need to do 12 months view for each different sorting category.
I can still live with the dynamic view currently, what I do is that when I need to do update, I go for view which update index manually. I just need to run index overnight, or leave it running for few hours.
Just like to get some updates from people who have used other databases with this kind of view and complexities, well you know, users who don’t know about system, tend to complain a lot. Nevertheless, they will have to accept such limitation if they know it is a problem that still will exist even if one is using other databases such as Access, Paradox,or Oracle even maybe? etc.
Cheers.
Subject: RE: How does view refresh Notes compared against Access or other databases?
See, when you go and give details about WHY you have performance issues, then someone might give suggestions for work-arounds…
How about a form with an embedded, categorized view that shows a single category based on formula (say, categorize on
@text(DateFieldFromForm;“D3”)
which gives 11/2006 for the current month…
Then put formula in a field that chooses that category.
For a YTD report, categorize on year instead of month/year… hide the year column, and add a month column in whichever order you like.
Your YEP can then be a bit of LS that runs against the current view.
You could have the YEP (and the dates for the category selections) built by an agent in the early hours of the morning each day, and then you have a FAST, flexible report system.
Subject: RE: How does view refresh Notes compared against Access or other databases?
The agent for view, you mean to do the refresh, or to do some updates in some fields, in order to give me the YEP number? i.e YEP = YTD actuals + Forecast for remaining months.
My documents made up of a field called status.
If status is actual, it will pickup values from ActualField.
If status is forecast, it will check which month is it now, say now is November, so it will take values from DecField up to MarchField (my financial year end is March 2007).
You are suggesting embedded view, is it because to reduce number of view, and thus, better performance?
I have not able to do agent via server update yet, as I am only testing using client currently.
Thank you very much.
Subject: RE: How does view refresh Notes compared against Access or other databases?
If you have a time sensitive calculation, the trick is to move the time sensitive calculation out of the view and into a scheduled agent which will run periodically.
For example, suppose you have a view in which you want to display documents which are ‘overdue’ by at least 30 days.
In the selection formula you could have the following time-sensitive selection formula (assuming that dueDate is a NotesDateTime field):
select @adjust( dueDate ; 0; 0; 30 ; 0 ; 0 ; 0 ) > @now ;
The problem with this simple looking formula is that, for any given document, it will potentially give a different answer everytime @now changes, which it will do every second.
Hence, everytime you (or anyone else) open the view, Notes has to look at all the docs and figure out whether to include it in the view.
To side-step this problem you could create a field on your document called, say, daysOverdue, which would be a number. It will be a computed field and it’s formula would be daysOverdue.
The selection formula for the view now becomes much simpler:
select daysOverdue > 30 ;
The final part of the trick is to have an agent which runs once per day (usually just after midnight) and updates the value of the daysOverdue field.
The agent could look something like this:
secsPerDay := 246060 ;
days := @Integer( (@now - dueDate ) / secsPerDay ) ;
@SetField( “daysOverdue”; days ) ;
The net result is that your time sensitive calculation will now only be executed once per day per document rather than once per doc everytime the view is opened. This means that the view index will only need to be built once per day rather than every time it’s opened.
Tortoise → Hare
Frunobulax
Subject: RE: How does view refresh Notes compared against Access or other databases?
Tqvm, Mr Frunobulax, now I got a clearer picture.