Bug 464828 - [tern] mitigate delay when first using assist
Summary: [tern] mitigate delay when first using assist
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: JS Tools (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 9.0   Edit
Assignee: Michael Rennie CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 432940
Blocks:
  Show dependency tree
 
Reported: 2015-04-16 15:05 EDT by Michael Rennie CLA
Modified: 2015-04-17 13:07 EDT (History)
1 user (show)

See Also:


Attachments
proposed fix (1.60 KB, patch)
2015-04-17 11:20 EDT, Michael Rennie CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2015-04-16 15:05:01 EDT
When you first load a page and immediately do a content assist, there is a slight delay. We should investigate sending a few requests to the worker right after it starts to 'prime the pump' so-to-speak, and see if we can get rid of the delay.
Comment 1 Curtis Windatt CLA 2015-04-16 15:24:50 EDT
I have found that it can be more than a slight delay (several seconds).  Long enough to make you think content assist is broken.
Comment 2 Michael Rennie CLA 2015-04-17 11:20:48 EDT
Created attachment 252495 [details]
proposed fix

Here is a proposed fix that sends an empty request to the server during the startup phase, which causes all the plugins, etc to be loaded. So by the time you ask for proposals there is no lag. This *should* also speed all requests to Tern (rename, find decl, etc) as it will already be loaded and initialized.
Comment 3 Michael Rennie CLA 2015-04-17 13:07:14 EDT
Pushed updated version of the patch to:

http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=84885b6f235b96d3ada1804aff7c891a79f91cf4

Closing fixed. If we find it does not work 100% of the time we can reopen.