chrome/common/extensions/docs/server2/cron.yaml - Issue 10829348: Extensions Docs Server: Large performance increase

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome/common/extensions/docs/server2/cron.yaml

Issue 10829348: Extensions Docs Server: Large performance increase (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: server is fast Created 8 years, 4 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« chrome/common/extensions/docs/server2/appengine_wrappers.py ('K') | « chrome/common/extensions/docs/server2/branch_utility.py ('k') | chrome/common/extensions/docs/server2/example_zipper.py » ('j') | chrome/common/extensions/docs/server2/file_system_cache.py » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 cron:

	2 - description: Load everything for trunk.

	3 url: /cron/trunk

	4 schedule: every 5 minutes
	not at google - send to devlin 2012/08/20 05:27:10 This means that the worst case is 10 minutes for a This means that the worst case is 10 minutes for a refresh, right? The best case being that the cronjob finishes and right afterwards the memory refreshes. The worse case being that the memory refreshes and right afterwards the cronjob refreshes, meaning it'll be another 5 minutes before the memory refreshes. Just something to observe...
	5
	not at google - send to devlin 2012/08/20 05:27:10 Another comment: we need to be careful with races Another comment: we need to be careful with races. What if somebody adds an API and its page, the cronjob finds the page, the memory refreshes and then the cronjob finds the API? We'll end up with a broken link. And I wonder if there are more insidious things that could happen. Just another thing to observe... I think we can get memcache/datastore to do atomic writes. Something to look into later (but keep it in mind). cduvall 2012/08/20 21:28:09 Both good things to think about. Thanks. Show quoted text On 2012/08/20 05:27:10, kalman wrote: > Another comment: > > we need to be careful with races. What if somebody adds an API and its page, the > cronjob finds the page, the memory refreshes and then the cronjob finds the API? > We'll end up with a broken link. > > And I wonder if there are more insidious things that could happen. > > Just another thing to observe... I think we can get memcache/datastore to do > atomic writes. Something to look into later (but keep it in mind). Both good things to think about. Thanks.
	6 - description: Load everything for dev.

	7 url: /cron/dev

	8 schedule: every 5 minutes

	9

	10 - description: Load everything for beta.

	11 url: /cron/beta

	12 schedule: every 5 minutes

	13

	14 - description: Load everything for stable.

	15 url: /cron/stable

	16 schedule: every 5 minutes

OLD	NEW