Skip to content
This repository has been archived by the owner. It is now read-only.

Seriously Slow Performance, crawling #208

Closed
macosforgebot opened this issue Feb 13, 2008 · 4 comments
Closed

Seriously Slow Performance, crawling #208

macosforgebot opened this issue Feb 13, 2008 · 4 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Feb 13, 2008

silas@… originally submitted this as ticket:252


We've implemented iCal and are having some serious performance issues. iCal server stats as reported by caladmin: 162 accounts, 65 calendars, 100 groups, 3000+ events, disk usage is 30kb on Intel Xserve Leopard server 10.5.2 with 54 OD accounts. We have all users calendars delegated to all other users, and about half of those users viewing all others calendars. We have a good DNS and resolution. When a user opens their iCal it may take up to 20 minutes to an hour or more for their calendar to sync, and the server pegs out at 75-100% cpu usage for all the python processes _Calendar user. Not to mention that it takes forever for iCal to display the available calendars for access in the preferences. All machines are leopard and bound to the OD, single server setup. Please let me know if I can help.

Unknown if this is related or not but provided in case it is, Sunbird will not connect to any users calendar for the few windows clients, error "not a dav collection or not available"

Silas Thomas silas@… International Affairs University of Oregon

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Apr 16, 2008

@wsanchez originally submitted this as comment:1:⁠ticket:252

  • Status changed from new to assigned
  • Milestone set to 1.x

Performance appears to degrade quickly when lots of delegates are in play, and you seem to have all users as delegates of all other users…

Need to look into what we can do to optimize the common queries, perhaps even caching responses.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Apr 18, 2008

@wsanchez originally submitted this as comment:2:⁠ticket:252

  • Milestone changed from 1.x to 2.x
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Oct 28, 2008

@wsanchez originally submitted this as comment:3:⁠ticket:252

  • Summary changed from Seriously Slow Perfromance, crawling to Seriously Slow Performance, crawling
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Dec 9, 2008

@wsanchez originally submitted this as comment:4:⁠ticket:252

  • Status changed from assigned to closed
  • Resolution changed from to Software changed

We've done a lot of work in version 2 to address these problems, including much better performance with respect to delegate queries and caching of common responses to clients.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.