irq

13/12/2015

“ The exponential growth in data traffic puts ever-increasing demands on the packet processing elements in the network, resulting in a need for high performance IP packet handling. OpenFastPath is an open source implementation of a high performance TCP/IP stack that provides features that network application developers need to cope with today’s fast-paced network. „

OpenFastPath | The OpenFastPath project page

(Source: openfastpath.org)

Quote posted at 00:11 Comments

04/11/2015

(via xkcd: Water Delivery)

(Source: xkcd.com)

Photo posted at 12:54 Comments

08/09/2015

“

QJump is a simple approach that improves latency determinism in datacenter networks. It works by employing two techniques:

1. rate-limiting the input into the network, so that long queues cannot build up; and
2. prioritizing traffic in the network, so that different applications can use rate-limits that suit them best.

With QJump, traffic from latency-sensitive applications (e.g., memcached) can “jump-the-queue” over traffic from latency-insensitive applications (like Hadoop). At the same time, traffic from many instances of memcached is rate-limited, so that they do not interfere with each other, while traffic from Hadoop runs without rate-limits and achieves full network utilization.

„

QJump - By CamSaS

(Source: cl.cam.ac.uk)

Quote posted at 12:13 Comments

23/08/2015

» Realities of Performance Appraisal

(Source: blog.learningbyshipping.com)

Link posted at 13:52 Comments

13/08/2015

(via Bits or pieces?: On the future.)

(Source: blog.gardeviance.org)

Photo posted at 11:59 Comments

03/08/2015

“ Adrian sees it as a calculated risk. “You’re gambling that the ecosystem is going to grow faster and bigger,” he says, “rather than 100 percent control of a small ecosystem, you become a dominant player in a much bigger ecosystem.” „

TNS Analysts, Show 55: Google, Docker and the State of Open Source Projects - The New Stack

(Source: thenewstack.io)

Quote posted at 11:03 Comments

16/06/2015

“ I’ll paint a stark picture: Given a piece of code that is absolutely optimal — it is faster than any other piece of code that does the exact same thing on earth, only no one knows now it works except the author — versus a piece of code that was written by someone in order for it to be augmented, modified, adapted, flexible and all of these things, I would take the latter. „

Microservices, monoliths and laser nail guns: Etsy tech boss on finding the right focus — > S C A L E — Medium

(Source: medium.com)

Quote posted at 14:12 Comments

22/05/2015

“ First, assembling the right team. (That means) hiring, certainly, but it also means parting ways with folks that just aren’t cutting it…making sure that we’re paying attention to that team dynamic and [that] it’s collaborative and it’s really challenging itself. Number two is making sure decisions are being made. I say that if I have to make a decision, we have an organizational failure. (That’s) because I don’t have the same context as someone who is working day to day with the data, with the understanding of the customer. I definitely see the organization and the people in it as the ones to make the decisions, because they have the greatest context for what needs to be done. „

Jack Dorsey: Twitter co-founder, Square CEO, punk | Marketplace.org

Quote posted at 00:26 Comments

09/05/2015

“

Modern software engineering is built upon abstractions that allow programmers to manage the complexity of ever-larger systems. Abstractions do this by simplifying or generalizing some aspect of the underlying system. This doesn’t come for free, though—simplification is an inherently lossy process and some of the lost details may be important. Moreover, abstractions are often defined in terms of function rather than performance.

Somewhere deep below an application are electrical currents flowing through semiconductors and pulses of light traveling down fibers. Programmers rarely need to think of their systems in these terms, but if their conceptualized view drifts too far from reality they are likely to experience unpleasant surprises.

„

Evolution and Practice: Low-latency Distributed Applications in Finance - ACM Queue

(Source: queue.acm.org)

Quote posted at 10:55 Comments

“ Most systems exhibit some variance in latency from one event to the next. In some cases the variance (and especially the highest-latency outliers) drives the design, much more so than the average case. It is important to understand which statistical measure of latency is appropriate to the specific problem. For example, if you are building a trading system that earns small profits when the latency is below some threshold but incurs massive losses when latency exceeds that threshold, then you should be measuring the peak latency (or, alternatively, the percentage of requests that exceed the threshold) rather than the mean. On the other hand, if the value of the system is more or less inversely proportional to the latency, then measuring (and optimizing) the average latency makes more sense even if it means there are some large outliers. „