Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
majke
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
32 ms
·
331.
▲
by
majke
9y ago
What I didn't mention in the article is a sea of corner cases around the SYN handling code. For example: did you know, that when SYN Cookies are disabled (sysctl set to 0), a quarter of slots in SYN Queue is reserved for "IPs that
332.
▲
SYN packet handling in the wild
(blog.cloudflare.com)
51 points
by
majke
9y ago
|
5 comments
333.
▲
by
majke
9y ago
(author here) That's the intention! Protocol development, protocol testing. Think - leap seconds. While we don't support having different timer for each process yet, this is easy to imagine. Also - this is somewhat similar to gola
334.
▲
Bluemonday: a fast HTML sanitizer to scrub user generated content of XSS
(github.com)
1 points
by
majke
9y ago
|
0 comments
335.
▲
by
majke
9y ago
Ok, I'll chime in here since all the comments are missing the point. If you are excited by golang-style in C, then Mr Sustrik's libmill is for you http://libmill.org/tutorial.html LibDill is a thin experiment &quo
336.
▲
by
majke
9y ago
Ha! There are maaaany opinions in this thread, but I will add mine. I'm not a fan of writing stupid mocks. That doesn't give me much confidence, and spending time on tests is mostly about building ones confidence. I very much pre
337.
▲
by
majke
9y ago
The map itself http://www.lyonwj.com/pp-viz/heatmap/
338.
▲
Golang’s Real-Time GC in Theory and Practice
(making.pusher.com)
2 points
by
majke
9y ago
|
1 comments
339.
▲
GPON Fibre to the Home networks insecurity
(pierrekim.github.io)
2 points
by
majke
9y ago
|
0 comments
340.
▲
“V8 will work well in any application, provided that it is called Chrome” (2010)
(gist.github.com)
3 points
by
majke
9y ago
|
0 comments
341.
▲
ARM Takes Wing: Qualcomm ARM vs. Intel CPU Comparison
(blog.cloudflare.com)
77 points
by
majke
9y ago
|
8 comments
342.
▲
REUSEPORT: How to achieve perfect packet locality (and 3 epic SystemTap scripts)
(blog.cloudflare.com)
3 points
by
majke
9y ago
|
0 comments
343.
▲
by
majke
9y ago
Bryan Cantrill at Surge 2013 "Leadership Without Management: Scaling Organizations by Scaling Engineers" aka "Middle management, a toxin or a cancer?" https://www.youtube.com/watch?v=bGkVM1B5NuI He said
344.
▲
by
majke
9y ago
Pen and paper. I carry a notebook with me and rewrite the todo list (to a new page) every couple of days. This makes it very clear what is and what is not a priority. If I rewrite the same thing for tenth time, maybe it's not important
345.
▲
by
majke
9y ago
Comment from reddit: https://www.reddit.com/r/programming/comments/78f1if/why_doe... LIFO is also the strategy for Completion Ports in Windows: > Threads that block their execution on an I/O comp
346.
▲
by
majke
9y ago
Correct. The point is the worker may be relatively idle when it accepts() plenty of connections and the load only happens after that. When the requests on the connections start to flow. You can imagine a situation when a single worker gets
347.
▲
by
majke
9y ago
Imagine a HTTP server supporting HTTP keepalives. Say 10 new connections come in. Say on average they will all go to a single worker. Then say all of the connections request a heavy asset. You will end up with one worker handling these 10 c
348.
▲
by
majke
9y ago
Author here. There are three highlights in this blog post: - epoll() seem to have LIFO behavior which can result in uneven load balancing across workers (in case of accept()ing from a shared socket) - using REUSEPORT can worsen latency in a
349.
▲
by
majke
9y ago
My fav net.ipv4.tcp_mtu_probing=2 MTU probing / RFC4821! I spoke about it here: https://blog.cloudflare.com/path-mtu-discovery-in-practice/ There are a couple of issues. In old kernels it caused a "WARNING&q
350.
▲
by
majke
9y ago
Aye. Got it.
351.
▲
by
majke
9y ago
Hold your horses. It's not MSS clamping per se. It's the middle box MSS clamping. Say a middle box rewrites my SYN packet from my phone to have smaller MSS, from 1500 to say 1344. The other party (server) responds with 1500 MSS, a
352.
▲
by
majke
9y ago
Problem with MSS clamping - if the other party has MTU of 1500 but the Path has MTU of < 1344, then, what? Well, it's broken. The sending party doing MSS clamping, will get the ICMP probably dropped, and the fragments will likely
353.
▲
by
majke
9y ago
This is a subject for another blog post. Or a book! This problem has been excessively discussed in early IP days. The alternative to current model is to have a fixed packet size. This inherently means that for some media the packet size wil
354.
▲
by
majke
9y ago
By "transfer" here I mean a thing like a curl on a large file.
355.
▲
by
majke
9y ago
Check out the online ICMP / Fragmentation checker: IPv4 version: http://icmpcheck.popcount.org IPv6 version: http://icmpcheckv6.popcount.org If you see red - this means your ISP / cable modem is not really
356.
▲
by
majke
9y ago
> For large transfers The implicit assumption is that a fragmented packet will be slightly more than MTU. So for a large transfer - say N packets, of packet size MTU + 1 - you will see N "first fragments" fragmented to the size
357.
▲
Broken packets: IP fragmentation is flawed
(blog.cloudflare.com)
144 points
by
majke
9y ago
|
49 comments
358.
▲
Gatebot – a DDoS mitigation framework that allows us to sleep
(blog.cloudflare.com)
2 points
by
majke
9y ago
|
0 comments
359.
▲
by
majke
9y ago
Cloudflare | Engineer | San Francisco, London, Austin, Champaign | ONSITE https://www.cloudflare.com/careers/locations/ Cloudflare vision is to help to build a better internet. Cloudflare sits in front of your int
360.
▲
Meet Gatebot – a DDoS mitigation bot that allows us to sleep
(blog.cloudflare.com)
3 points
by
majke
9y ago
|
0 comments
More ›