Details
Bug
Closed
Critical
Description
testing with a full schedule no end on all shows, 24 shows a day (1 hour each)
is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time.
-- too much time is being spent doing separate commits to the db, there is a lot of room for errors during this time as well as conflicts could happen while db is not in a completed state.
is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time.
-- too much time is being spent doing separate commits to the db, there is a lot of room for errors during this time as well as conflicts could happen while db is not in a completed state.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Paul Baranowski [ paul ] | James Moon [ james.moon ] |
| Status | Open [ 1 ] | In Review [ 10000 ] |
| Assignee | James Moon [ james.moon ] | Paul Baranowski [ paul ] |
Ofir - please talk to James directly if you can reproduce that and explain to him how to reproduce it.
| Status | In Review [ 10000 ] | Resolved [ 5 ] |
| Original Estimate | 2 hours [ 7200 ] | 0 minutes [ 0 ] |
| Remaining Estimate | 2 hours [ 7200 ] | 0 minutes [ 0 ] |
| Assignee | Paul Baranowski [ paul ] | Ofir Gal [ ofir.gal ] |
| Resolution | Cannot Reproduce [ 5 ] |
James - "1) Add a single repeating show (daily)" I meant everyday of the week. not only 2 days. Please Skype me when you're in if you still can't reproduce it.
Please also create 2-3 shows that repeat every day before closing this ticket. I'm running on a VM which is much slower than your office PC.
Please also create 2-3 shows that repeat every day before closing this ticket. I'm running on a VM which is much slower than your office PC.
Show
Ofir Gal
added a comment - James - "1) Add a single repeating show (daily)" I meant everyday of the week. not only 2 days. Please Skype me when you're in if you still can't reproduce it.
Please also create 2-3 shows that repeat every day before closing this ticket. I'm running on a VM which is much slower than your office PC.
| Status | Resolved [ 5 ] | Open [ 1 ] |
| Resolution | Cannot Reproduce [ 5 ] | |
| Assignee | Ofir Gal [ ofir.gal ] | James Moon [ james.moon ] |
| Assignee | James Moon [ james.moon ] | Naomi [ naomiaro ] |
This should be easier for Naomi to do since she is in the same office as Ofir.
| Description |
1) Add a single repeating show (daily) 2) Navigate the Calendar to the next month Result - It takes 3-4 seconds to load the events in the next month. Need to test with the show populator tool, but its noticeably slower than it used to. |
1) Add a single repeating show (daily) 2) Navigate the Calendar to the next month Result - It takes 3-4 seconds to load the events in the next month. Need to test with the show populator tool, but its noticeably slower than it used to. ---------------------------------- finding this in logs 2011-11-21 16:09:14 CET LOG: incomplete startup packet 2011-11-21 16:09:14 CET LOG: received fast shutdown request 2011-11-21 16:09:14 CET LOG: aborting any active transactions 2011-11-21 16:09:14 CET LOG: autovacuum launcher shutting down 2011-11-21 16:09:14 CET LOG: shutting down 2011-11-21 16:09:14 CET LOG: database system is shut down 2011-11-21 16:09:16 CET LOG: database system was shut down at 2011-11-21 16:09:14 CET 2011-11-21 16:09:16 CET LOG: incomplete startup packet 2011-11-21 16:09:16 CET LOG: autovacuum launcher started 2011-11-21 16:09:16 CET LOG: database system is ready to accept connections testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. |
| OS | [Ubuntu 10.04] | [Ubuntu 10.10] |
| Description |
1) Add a single repeating show (daily) 2) Navigate the Calendar to the next month Result - It takes 3-4 seconds to load the events in the next month. Need to test with the show populator tool, but its noticeably slower than it used to. ---------------------------------- finding this in logs 2011-11-21 16:09:14 CET LOG: incomplete startup packet 2011-11-21 16:09:14 CET LOG: received fast shutdown request 2011-11-21 16:09:14 CET LOG: aborting any active transactions 2011-11-21 16:09:14 CET LOG: autovacuum launcher shutting down 2011-11-21 16:09:14 CET LOG: shutting down 2011-11-21 16:09:14 CET LOG: database system is shut down 2011-11-21 16:09:16 CET LOG: database system was shut down at 2011-11-21 16:09:14 CET 2011-11-21 16:09:16 CET LOG: incomplete startup packet 2011-11-21 16:09:16 CET LOG: autovacuum launcher started 2011-11-21 16:09:16 CET LOG: database system is ready to accept connections testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. |
1) Add a single repeating show (daily) 2) Navigate the Calendar to the next month Result - It takes 3-4 seconds to load the events in the next month. Need to test with the show populator tool, but its noticeably slower than it used to. ---------------------------------- finding this in logs 2011-11-21 16:09:14 CET LOG: incomplete startup packet 2011-11-21 16:09:14 CET LOG: received fast shutdown request 2011-11-21 16:09:14 CET LOG: aborting any active transactions 2011-11-21 16:09:14 CET LOG: autovacuum launcher shutting down 2011-11-21 16:09:14 CET LOG: shutting down 2011-11-21 16:09:14 CET LOG: database system is shut down 2011-11-21 16:09:16 CET LOG: database system was shut down at 2011-11-21 16:09:14 CET 2011-11-21 16:09:16 CET LOG: incomplete startup packet 2011-11-21 16:09:16 CET LOG: autovacuum launcher started 2011-11-21 16:09:16 CET LOG: database system is ready to accept connections testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. |
| Summary | Calendar is running slower than it used to | Need to start using transactions in show population code (speed up the calendar) |
| Description |
1) Add a single repeating show (daily) 2) Navigate the Calendar to the next month Result - It takes 3-4 seconds to load the events in the next month. Need to test with the show populator tool, but its noticeably slower than it used to. ---------------------------------- finding this in logs 2011-11-21 16:09:14 CET LOG: incomplete startup packet 2011-11-21 16:09:14 CET LOG: received fast shutdown request 2011-11-21 16:09:14 CET LOG: aborting any active transactions 2011-11-21 16:09:14 CET LOG: autovacuum launcher shutting down 2011-11-21 16:09:14 CET LOG: shutting down 2011-11-21 16:09:14 CET LOG: database system is shut down 2011-11-21 16:09:16 CET LOG: database system was shut down at 2011-11-21 16:09:14 CET 2011-11-21 16:09:16 CET LOG: incomplete startup packet 2011-11-21 16:09:16 CET LOG: autovacuum launcher started 2011-11-21 16:09:16 CET LOG: database system is ready to accept connections testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. |
testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. |
| Description |
testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. |
testing with a full schedule no end on all shows, 24 shows a day (1 hour each) is very slow when the calendar has to populate the events before displaying them, on month view can take 14-18 seconds just for the request to complete, this doesn't include event rendering time. -- too much time is being spent doing separate commits to the db, there is a lot of room for errors during this time as well as conflicts could happen while db is not in a completed state. |
| Assignee | Naomi [ naomiaro ] | |
| Fix Version/s | 2.1.0 - Beta 1 [ 10362 ] | |
| Fix Version/s | 2.0.0 [ 10462 ] |
| Fix Version/s | 2.2.0 [ 10363 ] | |
| Fix Version/s | 2.1.0 [ 10362 ] |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Not a Bug [ 6 ] |
1. created a show with repeating on 2 days( Thur, Fri)
2. set end date to "No end"
3. save and iterate to next month.
Result: all events loads within 1 sec.