A particular type of the OutOfMemoryError messages has recently started catching my attention – the issues triggered by misused ThreadLocals have become more and more frequent. In this post I explain the motivation behind ThreadLocal usage.
Using Packer to create CentOS and Ubuntu boxes is not difficult. If you want to follow along, I have prepared a Git repository ariya/packer-vagrant-linux which contains all the necessary bits to create CentOS 5.4 and/or Ubuntu 12.04 LTS 64-bit boxes.
Logentries processes over 10 billion log events every day. That’s quite a lot of data. So, the Logentries research team decided to take advantage of their unique position and set out to examine a sample of their overall user base for insights: 22 billion log events from over 6,000 Heroku applications.
The author was asked "how the whole 'Hacker News MongoDB random bashing' situation was dealt with from the inside." In this article, she explains her reaction and her strategies for handling such issues during her time at MongoDB.
Managers don’t want to think harder than they have to. They like simple rules of thumb. One of the most useful rules of thumb is the 80:20 rule. You can see obvious cases where the 80:20 rule applies in software without looking too hard. For example, 80% of performance improvements are found by optimizing 20% of the code.
Yesterday someone was looking at my code and said “uh, you’re using +T in a generic”, and I said “that’s a hipster feature of Scala, you don’t need to understand it, you just need to get it right so your code compiles.”
In my previous post I installed and configured Ghost and WordPress. The purpose of that blog post was to test relative performance of the 2 platforms to see which one could handle more load. Many requested another test where an opcode cache was in place for WordPress. So that is exactly what this blog post is about.
So Dropwizard seems to be the rage around Java / Scala developers today as an extremely clean and minimalistic framework for DTRS ("Doing The Right Stuff") when it comes to serving up thick clients with REST-ful data.
After finishing up the major change of moving Voron to a Write Ahead Journal, it was time to actually start doing some performance testing. To make things interesting, I decided that we shouldn’t just compare this in isolation, but we should actually compare it to its peers.