-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Does the SCHEMA cache actually work? #3663
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
Comments
Thanks for reporting the issue, do you have an idea how we could write a failing test for that? |
@woodardj I went back to the CLI options and yes, I believe you missed the |
Ah, thanks for circling back, @flovilmart — I must have come to a similar conclusion, as I have that |
enableSingleSchemaCache is true in your config? |
It is, I must have found it digging through source; our cache appears to be behaving as expected now. I probably found it and forgot to post back on this issue. |
Awesome :) we probably need to document that. Do you want to add a PR on https://github.com/parse-community/docs/blob/gh-pages/_includes/parse-server/cache-adapters.md or another section about using SchemaCache altogether? |
Can do!
…-Jonathan
On Wed, May 17, 2017 at 10:07 AM, Florent Vilmart ***@***.***> wrote:
Awesome :) we probably need to document that. Do you want to add a PR on
https://github.com/parse-community/docs/blob/gh-pages/_
includes/parse-server/cache-adapters.md or another section about using
SchemaCache altogether?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3663 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAiDSc9YjxPrttNv3wtDpkjULV9wkumHks5r6xtYgaJpZM4MnK97>
.
|
Thanks! Very appreciated!
|
Closing as not an issue with parse-server |
I've just enabled the RedisCacheAdapter, and by default, it seems to be caching users and roles just fine, and according to the TTL that I've set (on parse-server 2.3.7).
However, the __SCHEMA cache defaults to 5 seconds, which I'm not sure would be of any value. There's this note in the definitions file for the defaults: https://github.com/ParsePlatform/parse-server/blob/2.3.7/src/cli/definitions/parse-server.js#L215
If I set this property as a config when initializing ParseServer via:
schemaCacheTTL: 60 * 1000,
I see the keys accumulating in Redis, but every request appears to generate a new …__ALL_KEYS and …__MAIN_SCHEMA key, each of which contains identical data, rather than using the previously cached value.
Is caching the SCHEMA through the redis adapter working for anyone? What have I missed?
The text was updated successfully, but these errors were encountered: