Skip to content

Improve fetching cache from chained backend #20

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.

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

Merged
merged 1 commit into from
Jul 14, 2019

Conversation

tsteur
Copy link
Member

@tsteur tsteur commented Jul 4, 2019

refs #19

While profiling a production server noticed during a tracking request which takes like 50ms we spent 2.73 ms in doContains and 2ms in doFetch. Considering this is like 4% of the time spent of a tracking request in doContains() even though it's not needed. The other backends will silently fail anyway and return false when a cache is not contained in a backend. And sometimes they do the doContains in doFetch anyway (eg ArrayCache).

FYI @mattab

refs #19

While profiling a production server noticed during a tracking request which takes like 50ms we spent 2.73 ms in `doContains` and 2ms in `doFetch`. Considering this is like 4% of the time spent of a tracking request in `doContains()` even though it's not needed. The other backends will silently fail anyway and return false when a cache is not contained in a backend. And sometimes they do the `doContains` in `doFetch` anyway (eg ArrayCache).

FYI @mattab
@tsteur tsteur added this to the Current sprint milestone Jul 4, 2019
@tsteur tsteur merged commit b000c45 into small-mods-1.0.1 Jul 14, 2019
@tsteur tsteur deleted the performancechainpiwik branch July 14, 2019 20:55
@innocraft-automation innocraft-automation removed this from the Current sprint milestone Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants