Opening a DB SLOW for some

I am seriously puzzled - We have one DB (120MB) on the Domino server that I can access very quickly, on the other hand there are a few users that are accessing the same DB from within the same office I am in and there access time is terribly slow…really slow.

-The server as well as all client are on ver. 6.5.5.

-I am on 100MB connection to switch, slow user on 1GB.

-Same results when trying to access same DB on alternate location.

-I switch to my notes ID from slow system and I can access DB very quickly. Switch back to original user and access is slow.

-I uninstalled notes client, removed notes folder, reinstalled…same results…slow.

-I ran an updall, compact and fixup against this DB but same result, I access it quickly, other user is terribly slow.

-Both systems that are accessing this DB are same in HW.

What could possibly create this environment?

Any help would be greatly appreciated.

Puzzled and out of ideas.

Subject: Opening a DB SLOW for some

So access using your ID from any system is fast? Is your ID set to manager access with all the roles?

Sounds like you might have readers fields in the database which could cause this behavior. If there are alot of documents in the database and the users only have access to a handlful, when opening the database, domino needs to go through every document for determing what documents thier ID has access to.

Give the user with slow access temporary higher security in the ACL and see if that speeds things up. If so, you have identified where the slowdown might be happening.

Subject: RE: Opening a DB SLOW for some

Well to give you an idea of the size of the DB, it is 136MB with 8,606 documents within it.I also have to say that I’ve been working in notes/domino for only 4 months…sooooooo I am sort of strugglin to understand new lingo/rights/application tasks/background tasks…

I do appreciate any help

Subject: Opening a DB SLOW for some

1 motive that your server go slow is the client has worked in other server. To check is see the print panel of the lotus notes if conects in other server. The solution is erase the cache.ndk, and the first time don’t go extremely quick, go quite quick but not extremely but very Ok and the next day go perfectly.I investigate another motive to go slowly but not that you describe, I think is I compact every night and it’s possible with a big database the first time when it has been opened go slowly. Now I change the program I’ll put the parameter -s10.

I hope my help is useful for you.

PD: Excuse me for my English, I made a lot of grammar mistakes but I think everybody can understand me.

Subject: Opening a DB SLOW for some

I’m having the same problem. How did you solve this?

Subject: RE: Opening a DB SLOW for some

Hi Walter,

Have you followed the same steps as Ron?

JYR

Subject: Opening a DB SLOW for some

Hi,

Do you have any readers fileds?

How many documents?

Reader Fields:
http://www.redbooks.ibm.com/redbooks/pdfs/sg245602.pdf Performance Considerations for Domino Applications
IBM - United States Notes from Support: Reader Names fields can impact performance
Use of ReaderNames fields slows view performance in Notes - search Technotes Doc Number: 1097609

JYR

Subject: RE: Opening a DB SLOW for some

Thanks for replying - I checked with our programmer, she said there are no “readers fileds”.There are 8606 documents in this DB

Size of DB = 132MB.

I am the notes administrator, and the one person that is having slowness issues is the CIO and other VP’s. The CIO is an Author to this DB.

Subject: RE: Opening a DB SLOW for some

HI,

Tips for Enhancing and Troubleshooting Notes 6 Client Performance

http://www-1.ibm.com/support/docview.wss?rs=475&uid=swg27006235

or you can check those too:

Application Performance Tuning - Part 1
Application Performance Tuning - Part 2

JYR

Subject: Opening a DB SLOW for some

Ron,

You did great troubleshooting. It sounds like it must be:

  1. Your id opens the db and gets certain navigation/views, others open it and get different (slow) navigation/views, or

  2. The docs have reader names fields and you have access to all docs and they don’t.

If you think #1 might be true, then you have to go into the design to figure out what code is being triggered for you and for them, and see the differences. I’ve had apps that send mail, for example, unless the id being used is mine. That allows me to do some live testing without sending workflow emails all over the place. Maybe you have something like that going on?

Otherwise, I agree with the other response suggesting that you go back to their desk and switch to your id and change ACL to give them all [roles] that you have. Now switch to their id and open db. If fast, bingo. Either way, revert ACL until you figure out correct solution, of course.

regards,

raphael

Subject: RE: Opening a DB SLOW for some

These are all great suggestions. The first that I plan to do is that ACL issue, this to me seems the most logical. I will let you know the results…thank you again. I appreciate it.