Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Take a look at this: <a href="http://blog.stackoverflow.com/2009/04/podcast-50/" rel="nofollow">http://blog.stackoverflow.com/2009/04/podcast-50/</a></p> <p>EDIT: Difficult to find specific (confirmed) references however, this paper perhaps gives some information regarding this: <a href="http://people.mozilla.org/~dmandelin/tracemonkey-pldi-09.pdf" rel="nofollow">http://people.mozilla.org/~dmandelin/tracemonkey-pldi-09.pdf</a> and this blog post which appears related: <a href="http://andreasgal.wordpress.com/2008/08/22/tracing-the-web/" rel="nofollow">http://andreasgal.wordpress.com/2008/08/22/tracing-the-web/</a></p> <p>Might not be related as it is a Microsoft research paper from March 2010: <a href="http://research.microsoft.com/pubs/121449/techreport2.pdf" rel="nofollow">http://research.microsoft.com/pubs/121449/techreport2.pdf</a></p> <p>Pure speculative on my part but it appears (at least to me) that there are two major forms of performance, that at the developer level (IDE) and that at the compiler level which this subject of trace trees addresses hence the "continuous optomization" during execution to get the trace inline for the hot spots. This then leads me quickly to areas of optomization related to multi-cores and how to utilize the trace tree somehow in that regard (multi-core environments). Interesting stuff considering the currently theoretical non-static type speed speculation as compared to the speed winners in static type utilized in current C and the performance potential to be gained. I recall a discussion I had with a hardware engineer years ago (1979) where we speculated that if we could just capture the 'hot' execution paths we could get a huge gain in performance by keeping it "ready to run" in situ somehow - this was way prior to the work at HP in this regard (1999?) and unfortunatly we did not get further than the discussion stage due to other commitments. (I am rambling here I think...:)</p> <p>OR, was this just related to the GO language? hard to tell in some respects.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat were the (then) unpublished optimizations that Steve Yegge referred to in "Dynamic Languages Strike Back"?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMark Schultheiss
    1. USMark Schultheiss
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI haven't listened to the entire thing, but the transcript does not appear to make any reference to this subject. :(
      singulars
      1. PO
      1. USAdam Paynter
 

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