Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bnoordhuis
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
bnoordhuis
11y ago
It's in the works: https://code.google.com/p/v8/issues/detail?id=811 You can tell by the number of CLs that a lot of work has been done already but there are a few more still in progress. It's prob
2.
▲
by
bnoordhuis
11y ago
I've been going back and forth on this. On the one hand, I feel that positive discrimination is just as bad as the other kind and that its proponents are not thinking things through as clearly as they should. On the other hand, board m
3.
▲
by
bnoordhuis
12y ago
Interesting results, thanks for sharing. I can perhaps shed some light on the performance differences. > Buffer 4.259 5.006 In v0.10, buffers are sliced off from big chunks of pre-allocated memory. It makes allocating buffers a littl
4.
▲
Beyond Node.js Express: An Intro to Koa.js and a Preview of Zones
(strongloop.com)
15 points
by
bnoordhuis
12y ago
|
2 comments
5.
▲
by
bnoordhuis
13y ago
Libuv author here. Libuv doesn't try to be all things to all people - its main users are Node.js and Rust - but if you have suggestions on how to improve the API or the implementation, please file issues[1] or join us in #libuv on irc
6.
▲
by
bnoordhuis
15y ago
On and off kernel hacker here. Compile and test the release candidates Linus puts out every fortnight. When the inevitable breakage happens, use `git bisect` to track down the offending commit. It's tedious and time consuming but you will m
7.
▲
by
bnoordhuis
15y ago
That's a regression we'll probably have fixed in 0.6.1. Note that I/O read performance is up 35%, from 19.7 mb/s in 0.4 to 26.6 mb/s in 0.6.
8.
▲
by
bnoordhuis
15y ago
I suspect that it's a jab at ALSA which, for reasons unknown, ships with a full LISP interpreter[1] that it doesn't actually use... Lennart Poetering is the author of PulseAudio. He probably has a bone or two to pick with ALSA. [1] http://
9.
▲
by
bnoordhuis
15y ago
> Isn't Node.js single threaded ? Yes (for now, we might take up V8 isolates). > Would it not under-perform , say compared to Erlang or Netty, in a multi-core CPU. No. You can spin up multiple processes and handle the load with (for
10.
▲
by
bnoordhuis
15y ago
It's been fixed in master. 0.5.2 comes out tomorrow (if all goes well) and will also contain the fix. https://github.com/joyent/libuv/issues/112 for details.
11.
▲
by
bnoordhuis
15y ago
linux doesn't have kqueue. But kqueue is only an API, you could emulate it with io_submit() and io_getevents(). A bigger obstacle is that not all file systems support asynchronous I/O, the io_*() syscalls won't help you there.
12.
▲
by
bnoordhuis
15y ago
That was the impression I walked away with too: much CS ivory tower thinking, little real-world relevance. But they're only interviews, everyday life at Google is probably (hopefully!) different. As a counterpoint to the HR horror stories:
13.
▲
by
bnoordhuis
15y ago
There isn't a shred of the original mongrel parser left. I'm not 100% sure but http-parser looks more like it's inspired by nginx than that it actually contains nginx code. Disclosure: I know both http-parser and nginx fairly well. I'm one
14.
▲
by
bnoordhuis
15y ago
Maybe I can help. I'm relatively local (Gouda, ZH) and I've managed teams like the one you mention before. Shoot me an email, address is in my profile.
15.
▲
by
bnoordhuis
15y ago
The language was C and my solution (adapted to the article) was something like this: // TODO enforce! see also: soylent green #define MAX_AGE 100 struct student { const char *name; int age; }; struct
16.
▲
by
bnoordhuis
15y ago
> His grandmother knew radix sort. Radix sort? I read it as a trick question where the answer is 'hash table with numberOfYearsOld as the key'. I suggested that as the solution to an almost identical question when interviewing with Goog
17.
▲
by
bnoordhuis
15y ago
Sounds about right. My base salary, no benefits, would be about 58K a year if I worked full-time. This is in Rotterdam, where salaries are slightly lower than in Amsterdam.
18.
▲
by
bnoordhuis
15y ago
I hear you, threading in SM is indeed fraught with dangers. On the off chance that you're going to revisit it, the way to go is to compile with -DJS_THREADSAFE and register a callback with JS_SetGCCallback() that tells the VM when it's safe
19.
▲
by
bnoordhuis
15y ago
V8 is a single-threaded VM and I don't see that changing any time soon, it's very much married to Chrome's per-process model. SpiderMonkey doesn't have that drawback, it supports threads just fine. These guys have their work cut out for the
20.
▲
by
bnoordhuis
15y ago
You'll be hard-pressed to exhaust all ports: modern operating systems track connections by source address + source port + target address + target port. I wouldn't be surprised if the TCP sequence number is also part of the mix. TIME_WAIT ti
21.
▲
by
bnoordhuis
15y ago
Take the staged approach: 1. Begin with a simple JDBC-backed servlet + JSP web app, like a blog (boring, I now), and deploy it to a servlet container like Jetty or Tomcat. 2. Migrate your servlets to Spring MVC and all that that entails: cr
22.
▲
by
bnoordhuis
16y ago
Sounds promising. Is remote an option?
23.
▲
by
bnoordhuis
16y ago
> Don't things like real time linux or soft real time patches for linux help, though ? I don't see how it could. The CPU essentially drops everything it's doing when a packet comes in. Have that happen often enough and there won't be ti
24.
▲
by
bnoordhuis
16y ago
The problem is that a high-bandwidth link overruns the CPU with thousands of interrupts per second. It can paralyse the system, where the CPU is so busy handling I/O that it doesn't get around to actually scheduling processes. Disclaimer: I
25.
▲
by
bnoordhuis
16y ago
No. The main problem the event MPM addresses is HTTP keep-alive. With pre-fork and threaded, every connection takes up a process or thread. This sucks for keep-alive because it can take a while before the client issues the next request. The
26.
▲
by
bnoordhuis
16y ago
Different design goals. Apache is meant to be robust, extensible and portable. * Robust: that's reflected in its internal API that makes it near impossible to leak resources. * Extensible: witness the gazillion modules out there. * Portable
27.
▲
by
bnoordhuis
16y ago
Another vote for Nick Kew's book. He is a regular poster on the modules-dev mailing list[1], by the way. `httpd -X` and `gdb httpd $(pidof httpd)` are a great help when debugging. [1] http://mail-archives.apache.org/mod_mbox/httpd-modules-
28.
▲
by
bnoordhuis
16y ago
Apache hacker here. AMA.
29.
▲
by
bnoordhuis
16y ago
Sorry, I updated my comment just as you posted yours. But - and I don't want to sound pedantic - how is m^2 not exponential growth? Edit: mea culpa guys, I carelessly translated from Dutch. You're all right: quadratic, not exponential growt
30.
▲
by
bnoordhuis
16y ago
The author states that preprocessing takes O(m) time but that is on average. A quick review of the code makes me think that its worst case is actually on the order of O((s * (s + 1)) / 2), where s = m / 2. The Achilles heel is the hash func
More ›