Groupwise Client extremely slow moving between folders

Hi,

We're experiencing a very unusual issue with a single user where switching between folders can take up to 30 seconds, usually no less than 25 seconds. This problem only occurs in the Groupwise 2012 Windows client (12.0.2), but we experienced the exact same problem with the same user last year at this time with an earlier version of the 2012 client. What is strange is that not only is this the only user experiencing the problem, but there is no issue when accessing the account via web access or the Groupwise 8 Linux client. Last year we opened an SR with Novell for this problem but they were unable to resolve the issue and the only solution we came up with was to create a new account for the user and migrate all her email over. This was less than ideal, but the problem had dragged on for a month and we could not come up with a better solution.

It appears that the problem emerges when many hundreds of emails get filed, probably at least 2,000 items on a single day in this most recent case. After that, the client experiences this slow down on any computer, not just the user's computer.

I would appreciate any insight that would shed light on this problem.

Thank you.

Tags:

  • In article <ssmusupport.6h1r5z@no-mx.forums.novell.com>, Ssmusupport
    wrote:
    > It appears that the problem emerges when many hundreds of emails get
    > filed, probably at least 2,000 items on a single day in this most recent
    > case. After that, the client experiences this slow down on any computer,
    > not just the user's computer.
    >

    A key early step is to see what is really slowing down or what resource is
    getting pegged. Ideally if you can reproduce the problem on demand for
    this.
    Fire up Task Manager on the Client side. What is memory and CPU doing
    during this?
    Monitor the POA at the same time, either directly watching what is in the
    queues in via the http interface, and/or with GroupWise Monitor setup and
    watching. Direct with frequent refreshes is a bit better than the 5
    default scan cycle of Monitor.
    What is CPU and memory use on the server at this point? Network traffic?
    A packet capture of the traffic between the two. Even though it is
    encrypted, the number,size,and timing of the packets can tell us where the
    waiting actually is.

    Make sure there are no scheduled tasks going on at the time the problem is
    seen. Tasks such as an AV scan, backups, or GWchecks could be a
    frustrating coincidental timing to watch for, especially with a flipped
    AM/PM.


    Andy of
    KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi,

    Thank you for your reply and apologies for not getting back to you sooner. The user is now away on vacation and I'm able to to properly test the problem given your guidelines. First, when starting up the Groupwise 2012 client, the CPU utilization spikes to between 95-99% on the client machine and it takes about 30-35 seconds to load. On the server, there is no effect whatsoever. The top command indicates server load at between .09 and .65 or so. Looking at the monitor on the POA or Groupwise monitor there are no problems indicated, though I don't see any option to monitor a specific user. Do you any tips on how to use the monitor to get information on a specific user? I know I can check the messages, but really don't see any options that would help here.

    Thank you.
  • Has Novell asked you to get debug level logs from the POA? They should have. There are debug options which will indicate the time required for the POA to respond to client / servers requests.

    If you see very high utilization on the client side, that may mean the client is trying to sort the message lists - try using a different sort order.

    Is this with client / server mode or caching mode? Switch modes.

    Wireshark on the client can given you timing information as seen from the client. Use the Wireshark analysis functions.

    IF the problem occurs infrequently, e..g after periods of inactivity, like 40 minutes, this may be a different problem. If you login and switch between the same few folders, it should be very quick, if so, then the connection timeouts on the POA side are not an issue.

    We have seen AV software cause similar issues, try with AV disabled, see if the problem disappears.

    -- Bob