@SetViewInfo & Performance

HCL Domino Domino Forum
1

All - I wonder if anyone knows if @SetViewInfo gets calculated before Readers fields when a view opens? I have an application that uses SPOFU views, and these views get deleted at the application close. There are some performance problems on entry and closing of the database because of the creation and removal of the private view for the user (some of which may admittedly be bandwidth or server usage). Back in version 5 I toyed with an Embedded view instead of the private views, however there was a problem with opening another database from framesets (it would open it in a new window rather than using an existing window the database was open in), so this ended up being a no-go. I believe this last point is now fixed, so I was going to test the embedded view functionality again - however I wondered if @SetViewInfo may be a better way to go?

What is it’s performance like with Reader fields (necessary for security) - are all the documents still checked for security as the view opens or does it only check the filtered ones?

Just thought I would check before having to set up an environment…

Cheers

David

2

Subject: Performance of @SetViewInfo and categorized views generally

Almost anything would give you better performance than creating and deleting views every time the application is used.

The reason the view is so slow with readers fields in it, is that the Notes client keeps requesting documents view entries from the server until it has enough to fill a screen.

If you use a categorized view that does display empty categories, you should see more reasonable performance, because, since each category is a view entry that the user can view, you don’t have to examine every entry in the view to find enough to fill a screen. This is particularly the case if the categories are closed, I think.

So, yes, you should get better performance by using @SetViewInfo.

3

Subject: Many thanks

I’ll give it a test and let you know of any measurements/feedback

Thanks for replying