If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘Latency’, page 1:

“Multi-Coring” and “Non-Blocking“ instead of “Multi-Threading” – with a Script

posted April 17, 2018 by "No Bugs" Hare

Abstract:	My talk at ACCU2018
	[→]

Pages: 1 2 3 4

posted October 17, 2017 by "No Bugs" Hare

Quote:	“if we can commit several transactions at the same time – RDBMS needs to fsync() our DB logs to physical disks only once”
Another Quote:	“if going our preferred way of single-writing-DB connection – make sure NOT to use RDBMS-level Group Commit”
	[→]

posted August 8, 2017 by "No Bugs" Hare

Quote:	“trying to optimize out a 3e-7 performance hit is very rarely worth the trouble.”
Another Quote:	“With 4S/4U boxes having typical MTBFs of 3–5 years, the next question we should ask ourselves, is “Hey, will we really be able to write software which crashes much more rarely than that?””
	[→]

posted March 21, 2017 by "No Bugs" Hare

Quote:	“we realize that for some of the Clients – UDP just doesn’t work because of some weird firewall between Client and Server”
Another Quote:	“there is nothing to block us (so head-of-line blocking doesn’t apply)”
	[→]

posted March 14, 2017 by "No Bugs" Hare

Quote:	“Nagle’s algorithm aims to deal with those [CENSORED] developers who’re trying to send data over TCP in really small chunks (like 1 byte each time)”
Another Quote:	“it seems that “proportional rate reduction” (PRR, reportedly used by Linux kernels by default starting from 3.2) performs for gaming purposes a little bit better than the alternatives”
	[→]

posted March 7, 2017 by "No Bugs" Hare

Quote:	“the best we can hope when using a single TCP connection over 5%-loss channel – is having 1.5-second “lag spike” every 5 or so minutes, and a 3-second “lag spike” every 2 hours.”
Another Quote:	“we may already have the-information-we-need on the receiving host – but this information is hidden from us by layers of abstraction on receiving side”
	[→]

posted January 24, 2017 by "No Bugs" Hare

Quote:	“Burstable packet loss. May be caused by a neighbor preparing his breakfast”
Another Quote:	“if there is a NAT device on the way from your Client to your Server – a sudden IP change can occur with absolutely no notification to Client whatsoever.”
	[→]