Someone knows why Calendar 5.1 is slow showing user the data?

Hi,

I have a Calendar 5.1 and showing the data to the user is so slow. Changing type browser help already a bit, but not totally. Does someone know what preference I have to change maybe? My cal db is not corrupt and accessing teh ldap works fine too. Just the data transfer isn't very speedy!!

Thanks for the help.

[342 byte] By [709039] at [2007-11-25 4:42:49]
# 1

Hi,

I'm sorry that this is not an answer to your question but I'm experiencing the same problem. Have you found any useful information on tuning iCS - the only thing I have found is that on my E450 (3xCPU's) is that the CPU utilization for the CPU the http process is running on goes up to 100% for a short period of time while the data is being retreived for the user.

It appears as if the application is CPU bound.

If you have any information could you please let me know at sharris@myra.com

Regards - Steve Harris

709028 at 2007-6-29 3:19:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Calendar Server...
# 2
On top of that... :) How many CAL user do you have on your 3 CPU machine?
705349 at 2007-6-29 3:19:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Calendar Server...
# 3
On top of that... :) How many CAL user do you have on your 3 CPU machine?
705349 at 2007-6-29 3:19:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Calendar Server...
# 4

Hi,

I also experienced that problem. I advice to go to Calendar 5.1.1, because there they already made a few changes, so the rendering goes a bit faster.

When you use IE the rendering is also much faster then netscape browser. They both just render the data a bit different.

We also went to Calendar 5.1.1. because 5.1 was too slow!

I hope this helps a bit.

greetz,

MH

709039 at 2007-6-29 3:19:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Calendar Server...
# 5
Actually the cshttpd binds to a CPU. If you bind more than one cshttpd to one CPU one might experience the slowness...Bottomline is one should have #CPU = #cshttpd processes...as per my experience.Arun Addepalli
AndyAdd at 2007-6-29 3:19:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Calendar Server...
# 6

NOTE: If you are running 5.1 on WinNT only run one cshttpd process as there is a bug with session sharing between cshttpd processes if you have more than one. you will notice that a user will remove a calendar then go back and the calendar is still there! That is because of this issue resolved in 5.1.1.

One cshttpd process works fine for many users anyway. We have over 5000 on this one process and it is fast with low cpu utilization.

navin504 at 2007-6-29 3:19:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Calendar Server...