Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Lumpy performance of Schema.org site #1171
Issue seems to be around new instances spawned to handle load having to create their own in memory page cache. If you are unfortunate enough to get a new instance to service your request you have to wait whist it builds and caches pages to answer you.
Suggested investigation of use of NDB Cloud Datastore to create a single page cache to be shared by all instances.
Ndbpagestore into Makemake Copying notes from #1173 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.