Notes 6 client slow, stutter issue

We have rolled out Notes 6.01 client to approximately 35 users. All PC’s are P3 933mhz w/256mb ram. Users have noticed a performance hit versus their 5.x client. Many have complained about a stutter/pause issue with Notes 6.

Specifically, when typing an email, the “I” bar (cursor) freezes for 3-10 seconds. While frozen, if they continue typing, whatever they typed will appear once the cursor un-freezes. This does not happen to all users, and not all the time, but probably close to half.

I have read some posts in these forums which alluded to this problem, but no solution.

Anyone else experincing this problem? Any fixes? Workarounds?

Subject: Notes 6 client slow, stutter issue

We had this issue and turning off the compression in the Ports section of User preferences fixed it for us.

While it stops the hangs/stutters, it is disappointing that we can’t user this feature.

Subject: new INI setting

we implemented the following ini setting to revert to R5 mail polling:

NONEWMAILTHREAD=1

Subject: RE: Notes 6 client slow, stutter issue

I had simillar problem.But it was not the problem with mail files.

Another (huge) db was opened by users the same time. ( about 1 M of docs)

Problem disapeared after disabling unread marks for that DB

Subject: Notes 6 client slow, stutter issue

We have noticed the exact same behavior. But it goes away for a few weeks, then comes back.

Subject: Notes 6 client slow, stutter issue

We noticed that also - but have not determined the cause.

Subject: Notes 6 client slow, stutter issue

I am also experiencing this problem on one machine only. That machine, though, is monitoring transaction disk space through the admin client.

Subject: Notes 6 client slow, stutter issue

Try turning off the automatic refreshing of the inbox (in User Preferences/Mail). Not sure if that is the problem, but worth a try.

Jeff Eisen
Lotus Notes Technical Lead
Messaging and Collaboration
Lotus Software/IBM Software Group

Subject: Notes 6 client slow, stutter issue

Dear Hernan,

we also have seen this and especially for upgraded voersions deletion of cache.dsk /ndk fixed the problem for some.

Cheers

Heini

Subject: I’d try all the local stuff…

Deleting cache.dsk/ndk sounds like a good idea. These users have been upgraded apparently, are they using an upgraded version of their R5 bookmark database, or their workspace with an upgraded R5 desktop5.dsk? If so, what happens if you let them work with a new pure ND6 bookmark.nsf? Or a new desktop6.ndk?

Finally, does it happen when they work on server or also on local?