TCA and fair execution.
The metrics that
the FX industry must use.
DOWNLOAD
LMAX Exchange
In part one, we discovered that our multicast receipt thread was being stalled by page faults.
In part two, we’ll dig down into the causes of those page faults, and with some help from our friends at Informatica, get to the bottom of things.
Sy…
LMAX Exchange
We recently fixed a long standing performance issue at LMAX.
The path we followed to fixing it was sufficiently windy to merit a couple of posts.
In this first post we’ll define our issue and then attempt to figure out its cause.
Problem Ident…
LMAX Exchange
One reason that automated UI tests can be unreliable is that they tend to be sensitive to what else is on screen at the time and even things like the current screen size. Developers running the tests locally also find it annoying to have windows openin…
LMAX Exchange
A month or two ago I was asked by someone in our Operations team what clock synchronisation is and why we need to do it. I gave them a very basic few sentence answer. That got me thinking that I never read an easy explanation when I myself got started …
LMAX Exchange
Ever since I read some initial blogs posts about the upcoming eBPF tracing functionality in the 4.x Linux kernel, I have been looking for an excuse to get to grips with this technology.With a planned kernel upgrade in progress at LMAX, I now have acc…
LMAX Exchange
In my last couple of posts, I’ve been looking at how UDP network packets are received by the Linux kernel. While diving through the source code, it has been shown that there are a number of statistics available for monitoring receive errors, buffer ove…
LMAX Exchange
BackgroundAt work we practice continuous integration in terms of performance testing alongside different stages of functional testing.In order to do this, we have a performance environment that fully replicates the hardware and software used in our pro…
LMAX Exchange
So far we have:
LMAX Exchange
Last time we implemented a minimal detector, and I presented the code for the detector as a fait accompli. Let’s take a closer look at it. import java.nio.file.Files; import edu.umd.cs.findbugs.BugInstance; import edu.umd.cs.findbugs.BugReporter; import edu.umd.cs.findbugs.BytecodeScanningDetector; import edu.umd.cs.findbugs.classfile.ClassDescriptor; import edu.umd.cs.findbugs.classfile.DescriptorFactory; import edu.umd.cs.findbugs.classfile.MethodDescriptor; public class FilesLinesDetector extends BytecodeScanningDetector { private static final ClassDescriptor JAVA_NIO_FILES = DescriptorFactory.createClassDescriptor(Files.class); final… More How To Find Bugs, Part 2: Well, this is somewhat confusing and frustrating
LMAX Exchange
Findbugs is an incredibly powerful tool, and it supports running of custom detectors. However, the API for writing custom detectors is not well documented, at least as far as I’ve been able to find. So, as I started writing detectors, I’ve been working primarily off a process of trial and error. It’s likely there are… More How To Find Bugs, Part 1: A Minimal Bug Detector
