bwross

6 ms·

1.
by bwross 12y ago
If you look really closely at the noisy images, you can see little blotches that vaguely resemble the things the computer recognized them as.
2.
by bwross 12y ago
Show me your application and I'll tell you where it's either calling select() or is limiting connections to keep itself from locking up the OS.
3.
by bwross 12y ago
So the basic take away seems to be: don't bother using async patterns for single, low latency connections to a server on your local network. For anything where you're dealing with thousands of connections from random Internet host
4.
by bwross 12y ago
Also analogous to cooperative multitasking as used in the modern era in high performance server applications. To great success, I might add.
5.
by bwross 12y ago
Additionally, a TCP connection is essentially an operating system resource; you need to set aside a port and space for a send and receive buffer. It might seem fine for a client to open hundreds connections, but imagine being a server with
6.
by bwross 12y ago
Solutions that pull the TCP stack out of the kernel perform so much better because they're bypassing all the internal bureaucracy that the kernel otherwise performs to make it as easy as possible for userspace applications to use the n
7.
by bwross 12y ago
Just don't try to do TCP over tapes on a station wagon.
8.
by bwross 12y ago
The primary advantage GridFTP has over simply using tar+netcat for performance is that GridFTP can multiplex transfers over multiple TCP connections. This is helpful as long as the endpoint systems limit the per-connection buffer size to so
9.
Show HN: Ht.js: Where HyperText Meets JavaScript(github.com)
2 points by bwross 12y ago|0 comments