Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>(I'm not sure that the graphs you linked to qualify as an intensive task, but regardless)</p> <p>I've gotten good results by breaking up the tasks using timeouts. Say you're doing something like this:</p> <pre><code>var largeSelection = d3.selectAll('svg circle') .data(aReallyLargeDataset);// Expensive Bind Operation largeSelection.enter() .append('circle')// Lots of appending .attr('r', function() { /* expensive calculations */ return ... }); largeSelection// Many refreshes .attr('cx', function() { /* more expensive calculations */ return ... }); </code></pre> <p>That might take the browser 1 second to render (a long time, considering everything will be frozen during this task). You can make it better by breaking it up like so:</p> <pre><code>setTimeout(function() { var largeSelection = d3.selectAll('svg circle') .data(aReallyLargeDataset);// Expensive Bind Operation setTimeout(function() { largeSelection.enter() .append('circle')// Lots of appending .attr('r', function() { /* expensive calculations */ return ... }); setTimeout(function() { largeSelection// Many refreshes .attr('cx', function() { /* more expensive calculations */ return ... }); }, 100); }, 100); }, 100); </code></pre> <p>Sorry about the obnoxious nesting and timeouts. You could refactor/abstract it in a way that's more readable/scalable. In any case, breaking up the tasks this way gives the browser a chance to "breath" and update the DOM so that, from the user's perspective, the application doesn't seem "stuck".</p> <p>If that <em>still</em> feels sluggish, you can break things up even more:</p> <pre><code>var entering = largeSelection.enter() .append('circle');// Lots of appending setTimeout(function() { entering.attr('r', function() { /* expensive calculations */ return ... }); }, 100); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POJavascript running intensive visualization operation without freezing the browser
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmeetamit
    1. USmeetamit
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSorry for the late response, seeing that you are familiar with d3, I've extracted some part of my code available at [jsfiddle](http://jsfiddle.net/sGnEY/).You see, the selection as assumed by you in form of many circles isn't the issue, it's the histogram parameters binSize, interval and number of bins, all of which is computed by a single d3.layout.histogram method. I've mentioned that wrapping this in a setTimeout won't be of much help
      singulars
      1. PO
      1. USAshwini Khare
    2. COHey. Not sure: is the jsFiddle you provided supposed to be runnable? (It throws an error). The line where the histogram layout is created (which you marked "expensive operation"), how long does it actually take? I.e. if you put `var t0 = Date.now();` before it and then `console.log(Date.now() - t0, 'milliseconds')`, what do you get? If it's over 100ms, then you do need to break it up by rewriting it. Doing so would involve copying the layout code out of the d3 source and creating a custom layout that computes itself asynchronously and calls a callback when finished.
      singulars
      1. PO
      1. USmeetamit
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload