8000 Cache generated timezones · Issue #799 · collective/icalendar · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Cache generated timezones #799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
4 tasks
niccokunzmann opened this issue Apr 12, 2025 · 0 comments
Open
4 tasks

Cache generated timezones #799

niccokunzmann opened this issue Apr 12, 2025 · 0 comments

Comments

@niccokunzmann
Copy link
Member

Generating timezones takes a lot of time as we walk through the years.
It would be nice to speed this up.

My guess would be that people expect the same timezone name to also represent the same timezone as they are generated from the same source specification. So, I suggest that by default, we cache the generated timezones.

  • When a VTIMEZONE is generated, cache it
  • Use the cached VTIMEZONE instead of generating a new one
  • Only add deep copies of the cached VTIMEZONE to the calendar
  • empty the cache with the tzp change

See also
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@niccokunzmann
0