Hosting 5.0.2 and very happy :)

[keithop]

We've all been waiting for version 5 and 5.0.2 finally ironed out the last bugs we saw that were show stoppers for our hosted customers.

Upgraded all our servers today, all went perfectly and already had many customers emailing to say they love the new version!

Nice job guys!

All the best,
Keith

[uxbod]

Yeah I second that Upgraded over the weekend and all the niggly little buglets have gone. Well done the Zimbra team

[RyecoAaron]

Another good install here The web interface is even noticeably faster than 5.0.0!

[Rich Graves]

The web interface is even noticeably faster than 5.0.0!

Don't know why that would be.

Our last unresolved 5.0-specific annoyance is
incredibel cpu usage + annoying busy cursor flickering with 5.0.2

If you can convince your users to default to text compose, it's fine.

[jholder]

Originally Posted by Rich Graves

Don't know why that would be.

Our last unresolved 5.0-specific annoyance is
incredibel cpu usage + annoying busy cursor flickering with 5.0.2

If you can convince your users to default to text compose, it's fine.

Zimbra 5.0 is up to 50% faster than 4.5 because we now load javascript on the fly. In 4.5, we loaded everything at startup.

See http://www.zimbra.com/blog/archives/...y_loading.html

[Rich Graves]

Yes, logging in to 5.0 is fater than 4.5. but why would 5.0.2 be faster than 5.0.0?

Small nit with lazy loading: Rather than one long delay, we now get a series of small delays -- first use of calendar, first use of compose, etc. Ideal would be opportunistic loading -- pick up the other packages during background idle time. Unfortunately, JS doesn't do backgrounding.

[RyecoAaron]

Originally Posted by Rich Graves

Don't know why that would be.

Not sure... I had more than one user mention it out of the blue. I never told them I upgraded from 5.0.0 to 5.0.2 or even asked them to comment. Maybe they noticed something different because the border around the Zimbra logo when logging in is different between 5.0.0 and 5.0.2.

I didn't change anything else with the server either. Oh well. It is nice to hear good things once in a while

[sqb]

Yes, most of these delays are minor. However, in our case it is taking only about 20 seconds to load the inbox but then over a muinute to load the compose window - over an ADSL link with https.

This is driving our users nuts. I would much prefer one inital wait than this huge pause when users are ready for there first compose/reply.

Is there a way to turn off lazing loading or specifiy to preload the compose window?

[uxbod]

I am not seeing any of those sort of delays ? Is your server heavily loaded ?