Multiweek scroll / next / previous is too slow with multiple calendars
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(Not tracked)
People
(Reporter: trevmrgn+bug, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [closeme 2024-04-15])
Reporter | ||
Comment 1•18 years ago
|
||
Comment 2•17 years ago
|
||
Reporter | ||
Comment 3•17 years ago
|
||
Reporter | ||
Comment 4•16 years ago
|
||
Updated•15 years ago
|
Updated•14 years ago
|
Comment 5•14 years ago
|
||
Reporter | ||
Comment 6•13 years ago
|
||
Comment 8•10 years ago
|
||
Comment 10•4 years ago
•
|
||
(In reply to Wayne Mery (:wsmwk) from comment #9)
Richard, can you reproduce this?
In TB 91.4.0 (64-bit) I acknowledge there are room for improvement in term of performance when displaying Calendar views but the multiweek view does not show shocking performance when clicking next/previous button with my trackpad (don't use a mouse with wheel and don't have one at hand to test) with multiple calendars with or without offline support (a combination of both I have).
It is slow enough for me to see each event being drawn with multiple calendar but in overall does not take more than about 1s, so not a dramatic issue.
The performance to load an entire network caldav calendar with ~4000+ items remain very poor though (several minutes) separate bug was already filed long ago about such issue... especially affecting startup performance as then the offline support takes over, though I would rather work online at all time :-)
Opening and saving calendar items is rather slow as well...
Updated•3 years ago
|
Comment 11•1 year ago
|
||
Trevor does this reproduce for you?
Reporter | ||
Comment 12•1 year ago
|
||
For many years, I haven't had a problem. A recent update (maybe 115.8.0) slowed redrawing down again. There is a noticeable flicker again but scrolling is not delayed waiting for the redraw like it used to be. I am only using local calendars.
It would be good to see smooth scrolling of the calendar instead of the current jump scroll.
Comment 13•1 year ago
|
||
Thanks Trevor. Let's see whether the next version helps resolve that more minor issue
Description
•