Delay predictor DB access until after the first main frame load complete.

Delay predictor DB access until after the first main frame load complete.

There might be better notifications to use, but at least allowing the main frame to complete one load should speed up initial boot.

BUG=136602
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=154301

[Shishir, 2012-08-30 18:51:08]

https://chromiumcodereview.appspot.com/10918007/diff/1/chrome/browser/predict...
File chrome/browser/predictors/autocomplete_action_predictor.cc (right):

https://chromiumcodereview.appspot.com/10918007/diff/1/chrome/browser/predict...
chrome/browser/predictors/autocomplete_action_predictor.cc:97: HistoryService*
history_service = HistoryServiceFactory::GetForProfile(
Does it make sense to move this to onload too?

[dominich, 2012-08-30 18:53:57]

https://chromiumcodereview.appspot.com/10918007/diff/1/chrome/browser/predict...
File chrome/browser/predictors/autocomplete_action_predictor.cc (right):

https://chromiumcodereview.appspot.com/10918007/diff/1/chrome/browser/predict...
chrome/browser/predictors/autocomplete_action_predictor.cc:97: HistoryService*
history_service = HistoryServiceFactory::GetForProfile(
On 2012/08/30 18:51:08, Shishir wrote:
> Does it make sense to move this to onload too?

In most cases that I've seen, it's already loaded at this point so it's not the
bottleneck. It's certainly something that could be done but it would complicate
the startup of this object significantly.

If the change in this CL doesn't significantly reduce the startup time (which I
believe it will) then I can revisit this.

[Shishir, 2012-08-30 18:55:47]

lgtm

[commit-bot: I haz the power, 2012-08-30 19:49:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dominich@chromium.org/10918007/1

[commit-bot: I haz the power, 2012-08-30 23:10:17]

Change committed as 154301