SWA serious performance issues

[anthony.hardy]

I obviously have some setup/tuning issues with SWA. I had scalix 11.4.2 running on a standalone box (older hardware). I migrated (successfully) to a virtual environment, giving the server a 64bit OS (RH5) and 6G ram.

I "time out" after a minute or so after logging into SWA. This is confirmed with 3 users (we have 170-180 users). I've looked everywhere to get performance tuning tips. I've tried tuning postgres, tomcat, etc and Outlook seems to have seen a performance boost and other imap clients (squirrelmail) have DEFINITELY seen a HUGE performance boost . . but SWA just sucks, performance wise.

The "time out" is an error "Your request to the server has timed out, keep trying?"
I don't see anything on consequence in catalina.out . . . . I'm working to get anything from scalix-swa.log right now.

I have a secondary scalix server as part of my licensing that is for our students (about 1200 of them). It seems to be experiencing the same issues. I'm going to have some REALLY upset people tomorrow when they can't get to their email for their online courses.

Yes, I've deleted imap cache. Things were slow on the previous hardware (much too slow, after watching outlook web users login, I'm embarrassed to be using scalix). I'd really appreciate it if you guys could help me get "un-embarrassed."

[RSisco]

We were having the exact same issue (with all 9 of our users). Nothing I tried was working, so on a prayer I upgraded to 11.4.5 and voila, the problem was solved. The error went away and SWA worked faster and more reliably than it ever had.

Richard

[anthony.hardy]

Thanks Richard. We just renewed our annual upgrade contract in June and I didn't read the instructions for 11.4.5 close enough, so we went from 11.4.2 to 11.4.4 since our licensing key was 6.24-2009. This could be the result of a config change on reinstall for the new box or just the upgrade to 11.4.4.

Just an FYI, I upped the old box to 11.4.4, ensure everything was functional (for about 30 miunutes), and then shut down scalix services. I installed on the new box, then copied the message store over (same uid and gid).

If I restart tomcat, I can get in for a while (not too long, maybe 5-10 mins).

I've contacted scalix (through the about/contact page, as recommended, which is just too weird btw) to get a lic key that will work for 11.4.5 in hopes that will work.

[tonysu]

Don't know if this might relate to your situation,

But recently i've discovered a likely correlation between the "time out" error and when the Server is likely doing something rather intensive like a regular maintenance chore, in my case it looks like it's doing mailbox cleanup on its own schedule likely related to the messages being permanently deleted.

I haven't yet looked closely at whether it's possible to over-ride what appears to be randomly timed maintenance operations, would be cool if those kinds of operations only were executed on a schedule.

Maybe this should be a "Feature Request" that during the Install/Setup scheduled maintenance should also be setup at that time and it should be enforced.

Tony

[anthony.hardy]

I'm upgraded to 11.4.5 and so far so good. No timeouts yet. Loads are much better so far and response/load times in SWA are doing quite well . .but it's only been 5 minutes:). I'll post back here when I'm sure this is corrected.

[anthony.hardy]

OK, so far so good. We've been stable and functional since the upgrade from 11.4.4 to 11.4.5. Man, that was no fun.

If this situation changes, I'll be sure to post back here.

[astring@magbelle.com]

Anthony,

Another answer would be to call someone in your local area that knows a lot
about Scalix. If he's not too busy with grad school, he'd probably
help you out. But you have to buy lunch.

Sorry you had problems, call me tomorrow and I'll give you my cell number.

Allen