11–20 of 29 posts
How can this even exist without generics, template meta-programming or a turing complete type system? I doubt that they know what they're doing.
So, I guess your sarcasm was a bit too subtle. This one is better :)
[1] http://www.reddit.com/r/programming/comments/10zsz4/i_wrote_...
How can this even exist without generics, template meta-programming or a turing complete type system? I doubt that they know what they're doing.
The first time I read one of these comments by you on reddit[1] I thought it was sincere - replies to it suggested I was not alone, although I was surprised that one was on your side. So, I guess your sarcasm was a bit too subtle. This one is better :) [1] http://www.reddit.com/r/programming/comments/10zsz4/i_wrote_...
If you need less than 200 DNS lookups per second per DNS server the Perl version is fine and might be a little easier to setup. The Go version is much faster (in prodution we've seen it do 5-6000 requests a second on commodity hardware and even virtual servers).
Is 6000 rps a high number for a DNS server? Let me do a back of the envelope calculation: one simple dns request (assuming udp here) response msg size is 100bytes, 6000rps x 100bytes /1024/1024 x 8 = 4.69mbps. Even we consider the request msg size is equal to that of response msg, the throughput is still 9.38mbps, far from saturating the network pipe. It sounds to me there is still space for improvement.
For people searching for performance benchmarks like me, here are the numbers I dug around from the post ( http://geo.bitnames.com ) If you need less than 200 DNS lookups per second per DNS server the Perl version is fine and might be a little easier to setup. The Go version is much faster (in prodution we've seen it do 5-6000 requests a second on commodity hardware and even virtual servers). Is 6000 rps a high numbe…
I'm in love with Go. The more I use it the more i fall in love with it.
For people searching for performance benchmarks like me, here are the numbers I dug around from the post ( http://geo.bitnames.com ) If you need less than 200 DNS lookups per second per DNS server the Perl version is fine and might be a little easier to setup. The Go version is much faster (in prodution we've seen it do 5-6000 requests a second on commodity hardware and even virtual servers). Is 6000 rps a high numbe…
Was it implied that the 6000 requests was peak performance of the software, or was it just the current max usage they've seen?
http://www.pool.ntp.org/en/join.html
My firewall at home is part of the pool. You can configure how much traffic you can handle in the manage servers interface. With any decent cable connection you can set the speed to 768Kbit and never notice the traffic (ntp is just tiny udp datagrams).
While we are at it lets go through /etc/ntp.conf and remove any references to stratum one servers. With a recent version of ntp you can replace all of your server lines with:
pool 0.CC.pool.ntp.org iburst
pool 1.CC.pool.ntp.org iburst
pool 2.CC.pool.ntp.org iburst
pool 3.CC.pool.ntp.org iburst
pool CC.pool.ntp.org iburst
More info on using the pool can be found here:
For people searching for performance benchmarks like me, here are the numbers I dug around from the post ( http://geo.bitnames.com ) If you need less than 200 DNS lookups per second per DNS server the Perl version is fine and might be a little easier to setup. The Go version is much faster (in prodution we've seen it do 5-6000 requests a second on commodity hardware and even virtual servers). Is 6000 rps a high numbe…