Monday, January 5, 2015

"Optimizing Go: from 3K requests/sec to 480K requests/sec"

480K TPS would be a wonderful problem to have but in the meantime I think this sort of transaction volume has a limited number of contestants. Just how many companies do work at netflix, google or amazon scale? Not many.

The thing to remember is that evil Big-O notation from those college days. Adding the fewest LOC could cause the 480K to fall like a rock. Every bit of work you ask the transaction to perform could have a drastic effect.

For example; let's say that the 480K is just counting the number of transactions... nothing else. If you decided to add the number a second time then you'd also expect the TPS rate to be half. This becomes more relevant when that "second" thing is much more costly.

No comments:

Post a Comment

static site generators

Static site generators are pretty cool. Granted they are an oversimplification of the java/json/xml/xslt site manifestation from the olden d...