-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream 15x slower when JS devconsole is open #610
Comments
What version of Chrome are you using? I want to rule out the following bug(s): On Mon, Jul 13, 2015 at 4:09 PM, Adam Sadovsky notifications@github.com
|
Linux Chrome, Version 43.0.2357.132 (64-bit) |
It sounds like the second bug isn't fixed it. Maybe we should use exorcist? |
We already use exorcist and extract the sourcemap into a separate file. |
That said, -rw-r----- 1 sadovsky eng 1.1M Jul 13 17:08 bundle.min.js |
@asadovsky Do you have "async stack trackes" and/or "pause on exceptions" enabled in your dev console? With both of those options enabled, my benchmark takes ~14 seconds.
With both of those options disabled, my benchmark takes ~7.5 seconds.
With the dev console closed, my benchmarks take ~4.5 seconds.
|
I don't remember what I had checked. I think I tried various combinations, but based on your numbers I'm guessing my 16x figure had both options checked. Thanks for looking into this! I'm going to implement my own logging helper that can write either to console.log or to a text log in the DOM. |
Closing this issue. The "async stack traces" and "pause on exceptions" were causing the slowness. Adam implemented a logger that writes to DOM, so we don't need that lousy dev console any more :) |
@nlacasse @bjornick @aghassemi @bprosnitz
As part of debugging poor todosapp->syncbase RPC performance, I added a benchmark that does 100 puts (in parallel), then scans the written records. I console.log() very little - just enough to know how long the operations took from the client's perspective. It turns out that simply having the devconsole open makes the scan ~15x slower - see below.
With devconsole open:
With devconsole closed (opened only at the end, to get console logs):
Note, the VDL scan API looks like this:
Where KeyValue is defines as such:
As another data point: running Scan using vrpc takes under 300ms.
To reproduce this, see instructions here:
$V23_ROOT/experimental/projects/todosapp/README.md
Run all the steps in the "Running the web application" section, then visit http://localhost:4000/?d=syncbase&n=/localhost:8200&bm=1 in your browser.
The text was updated successfully, but these errors were encountered: