Extensions Docs Server: Large performance increase

chrome/common/extensions/docs/server2/cron.yaml

Index: chrome/common/extensions/docs/server2/cron.yaml
diff --git a/chrome/common/extensions/docs/server2/cron.yaml b/chrome/common/extensions/docs/server2/cron.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..c36e8c1fe6dba9f63fde3e8c0862b4fe229ebd43
--- /dev/null
+++ b/chrome/common/extensions/docs/server2/cron.yaml
@@ -0,0 +1,16 @@
+cron:
+- description: Load everything for trunk.
+  url: /cron/trunk
+  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 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...

+

[not at google - send to devlin, 2012/08/20 05:27:10]

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.

+- description: Load everything for dev.
+  url: /cron/dev
+  schedule: every 5 minutes
+
+- description: Load everything for beta.
+  url: /cron/beta
+  schedule: every 5 minutes
+
+- description: Load everything for stable.
+  url: /cron/stable
+  schedule: every 5 minutes