Skip to content
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

Ndbpagestore into Makemake #1213

Merged
merged 3 commits into from Jun 17, 2016
Merged

Ndbpagestore into Makemake #1213

merged 3 commits into from Jun 17, 2016

Conversation

@RichardWallis
Copy link
Contributor

RichardWallis commented Jun 17, 2016

Retargeting #1173 to v3.1 instead of 3.0

@danbri
Copy link
Contributor

danbri commented Jun 17, 2016

Thanks!

@danbri danbri merged commit 9f2c02d into sdo-makemake Jun 17, 2016
@danbri
Copy link
Contributor

danbri commented Jun 17, 2016

In response to issue (#1171)
Overview:

Previously created pages are held in a within instance memory cache that is shared between threads. This means that each page is recreated for each application instance. We previously noted that the live site spawned off dozens of instances to support the load,
This version uses the Cloud Datastore to hold cached pages.
The single NDB store is shared between all threads of all instances.
​Should​ result in a lot less page creations, and more importantly you having to wait for a new instance to create you a page.
The NDB store is persistent so will keep the page store even when you reload/deploy a new version of the code/data.
Implemented code that detects this condition and deletes all pages in the store as it starts.
For early supporting there is a way to manually call this caheFlush function.

@danbri danbri deleted the ndbpagestore branch Aug 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.