Docserver: Make the hand-written Cron methods run first rather than last, since

Docserver: Make the hand-written Cron methods return a Future and run first
rather than last, so that they can be parallelised and have the most effect.
Implement a few of the more trivial Cron methods, including moving most
FeaturesBundle methods to return Futures.

BUG=305280
R=jyasskin@chromium.org
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=233427

[Jeffrey Yasskin, 2013-11-06 22:37:09]

lgtm

https://codereview.chromium.org/63203002/diff/50001/chrome/common/extensions/...
File chrome/common/extensions/docs/server2/cron_servlet.py (right):

https://codereview.chromium.org/63203002/diff/50001/chrome/common/extensions/...
chrome/common/extensions/docs/server2/cron_servlet.py:171: '%s: took %s seconds'
% (title, time.time() - start_time))
This may not be so useful anymore since even if the work is completely finished
by the .Get() call, you'll still get the time of the .Get call rather than the
time the action took. Maybe take a time for creating the future and a separate
time for running .Get() and add them?

https://codereview.chromium.org/63203002/diff/50001/chrome/common/extensions/...
chrome/common/extensions/docs/server2/cron_servlet.py:181: for future in
futures:
You could delay this loop until the end of the function, to give it more time to
overlap with rendering.

[not at google - send to devlin, 2013-11-07 00:14:47]

Committed patchset #5 manually as r233427.

[not at google - send to devlin, 2013-11-11 04:08:33]

submitted this ages ago, sending comments.

https://codereview.chromium.org/63203002/diff/50001/chrome/common/extensions/...
File chrome/common/extensions/docs/server2/cron_servlet.py (right):

https://codereview.chromium.org/63203002/diff/50001/chrome/common/extensions/...
chrome/common/extensions/docs/server2/cron_servlet.py:171: '%s: took %s seconds'
% (title, time.time() - start_time))
On 2013/11/06 22:37:09, Jeffrey Yasskin wrote:
> This may not be so useful anymore since even if the work is completely
finished
> by the .Get() call, you'll still get the time of the .Get call rather than the
> time the action took. Maybe take a time for creating the future and a separate
> time for running .Get() and add them?

Makes sense.

This logging is most for me to check to make sure nothing crazy is going on, but
separating out the times would be useful.

https://codereview.chromium.org/63203002/diff/50001/chrome/common/extensions/...
chrome/common/extensions/docs/server2/cron_servlet.py:181: for future in
futures:
On 2013/11/06 22:37:09, Jeffrey Yasskin wrote:
> You could delay this loop until the end of the function, to give it more time
to
> overlap with rendering.

Good idea.