Recent submissions

Comment · 4 months ago
If GOTW, actually means GWOT and Global War on Terror, please have courtesy of reading your posts beforehand, and perhaps also not assuming a US audience.
Comment · 1 year ago
Comment · 5 years ago
IDW - Intellectual Dark Web
Comment · 5 years ago
I nominate this essay, as Paul Graham's least controversial. Perhaps, someone who works with or in the non-profit sector could provide a counterpoint.
Comment · 5 years ago
Comment · 5 years ago
When you say 'defining languages', do you mean as DSLs or choosing appropriate existing languages? If DSLs, which language would you recommend for creating DSLs. Could you give a successful example?
Comment · 5 years ago
Yep, I looked at it again. My desire to be impressed with grandmaster foresight got the better of me.
Comment · 5 years ago
I think the move Rowson's referring to is move 9. Since in the essay he says "Yermolinsky offered a pawn as bait, and I very nearly didn’t take it because doing so would allow him to play a series of forcing moves"

So the only pawn that was offered and that Rowson took was on move 10 in reply.

The only reason I checked was to see how far a grandmaster was looking ahead, in this case 14 moves, which i find impressive. "...I discovered a surprising detail right at the end of the line, in which my knight could retreat back to its original square, "

Like you, I wouldn't be impressed if he only saw from move 18 to move 24.

Comment · 6 years ago
Pure speculation, isn't the most interesting time period in the signal the transition from signal to no-signal (and back again)? How high is the resolution of the sensors? Is it possible that some frequencies are blocked fractionally earlier than others? At a fine enough temporal resolution, there might be more clues regarding the source.
Comment · 6 years ago
Yes, I know. But the tone of the whole article, is as if, they've found deep flaws across many VMs. They call something 'warmup" which I think has little or nothing to do with the JIT, but is unaccounted variations in the whole running system.

The final graph shows a binary trees program in C, with a 6% variation between "in process executions", and no steady state, it seems logical that most VMs will show the same or worse variation.

The "warmed-up steady state" does exist, but not if they define it so narrowly. All of their iterations and timings are running at x30 to x100 interpreted speed, the only 'cold' interpreted code is in a few microseconds of the first loops of an execution.

Comment · 6 years ago
It seems that the authors are not measuring what they think they are, or have explained it poorly. Most transitions from interpreter to JIT show speedups of x10 to x100, eg luajit or V8. How is it possible that the variation of V8 (as an example), according to their numbers is showing improvements of only a few percent, when it should be orders of magnitude faster after transition? My conclusion, they are measuring variations after warmup.

All of the warmup, and transitions from interpreter, to JIT, to optimised JIT , happen inside the first few micro or milliseconds of EVERY one of their thousands of process iteration. Their measurements are ALL of the system variation of the VM after warm up has taken place. The VM is optimizing within the first 1-1000 inner loops occuring at the start of EACH process iteration. For most working programmers, a variation of a few percent on a running system AFTER warm-up in "steady-state peak performance", and before any I/O takes place (because language benchmarks avoid I/O), would not be an issue. If it is an issue, then the article perhaps demonstrates that a compiled language would offer less variation.

The benchmarks listed range from a shortest of around 0.4s for fannkuch/hotspot/linux, up to 1.8s for n-body, pypy, linux. This 'long-running' benchmark code (of .4 to 1.8s ), by definition, has to include multiple inner loops/hot code, which is quickly optimized, otherwise benchmark code would have to be millions of lines long, in order to have a sufficient runtime length. Tests need to run for at least tenths of a second, for cross language comparisons, since JITted languages take some iterations to warm-up.

Comment · 6 years ago
How long were you at google for, and how long since you left? Otherwise, the numbers don't offer much insight.
Comment · 7 years ago
I've googled generally and verbatim with various quotes from above and your name, and cannot find the essay. It sounds interesting. Can you post a link please.
Comment · 7 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton