search

kashiwazakinenji / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Modify Chromium SDK API to allow for lightweight Scripts objects #50

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
SDK/Debugger version: 0.3.0

The Script objects in the SDK always download their script data. This can 
significantly impact startup time for the debugger. Large scripts (600k-900k in 
our case) take around 1 sec to download even between processes on the same 
machine.

    JavascriptVm.getScripts(ScriptsCallback) throws MethodIsBlockingException;

In order to reduce the startup time of the debugger, I'd like the Script 
contents to only be loaded on demand, or to have additional API methods added 
to that you can determine which scripts are loaded into the target VM w/o 
downloading the content. In a nutshell, we want to know the script names, we 
don't use the script contents, and we don't want to pay the download cost for 
those contents. Thanks much!

Original issue reported on code.google.com by devonca...@gmail.com on 11 Sep 2011 at 3:40

GoogleCodeExporter commented 8 years ago

Original comment by peter.ry...@gmail.com on 11 Sep 2011 at 9:04

GoogleCodeExporter commented 8 years ago 
This requires SDK compatibility breakage.
Therefore should be planned for 0.4.0.

Original comment by peter.ry...@gmail.com on 15 Sep 2011 at 9:00

GoogleCodeExporter commented 8 years ago 
Hi Devon,

could you please update on how badly you want this feature? It is sure to break 
API compatibility, the question is whether you are ready to such trade-off 
right now?

Peter

Original comment by peter.ry...@gmail.com on 31 Oct 2011 at 4:29

GoogleCodeExporter commented 8 years ago 
This issue is less critical then it used to be. This was a feature request for 
the Dart --> JS debugger. The compiler we had been using created very large JS 
files, even for hello world-ish applications. On the order of several 
megabytes. We'll shortly be moving to a new compiler architecture which will 
output JS files in the 10's or 100's of KB range. While we'll still have to pay 
the download cost for scripts, the time should now be much more manageable. So, 
feel free to reduce the priority of this, or if you feel the cost for the API 
change would be too high, close the issue altogether. Cheers,

Devon

Original comment by devonca...@gmail.com on 31 Oct 2011 at 9:29

GoogleCodeExporter commented 8 years ago 
Closed per no interest from requester.

Original comment by peter.ry...@gmail.com on 19 Sep 2012 at 3:52