BREW MACVIM CANNOT ALLOCATE COLOR INSTALL

I readily concede that Graphite was not designed for the transient nature of the sort of bleeding-edge containerized, clustering systems that are becoming popular in conference talks and Hacker News (if not in actual use in production, but we'll forgive them this tiny oversight). It's almost as if they're trying to sell you something. And yet, what I find myself really disappointed over is the obvious misrepresentation of fact (as it pertains to Graphite's technical limits) and an almost malicious disregard for the enormous community that uses it and contributes back to its ongoing development. Many folks linked this article to me, almost certainly expecting me to respond in an uproar. There was an article published recently - not here, and not to be linked or referenced here directly - proposing that 'nobody loves Graphite' anymore. For this round I went with Synthesize v3.0.0RC2, which targets Graphite's master branch.

BREW MACVIM CANNOT ALLOCATE COLOR INSTALL

For the previous test I used Synthesize v.2.4.1 to install Graphite 0.9.15 on a 64-bit Ubuntu 14.04 LTS instance in Amazon's EC2 cloud. I neglected to mention this before, but all series of benchmarks started with installing Graphite using the Synthesize setup script. This round of tests used the same configuration and benchmarking processes as before. And while I've become very familiar with much of the code base over the course of writing The Graphite Book and have thrown a lot of traffic at it over the last few months, I hadn't run any significant tests for performance regressions at scale (compared to the 0.9.15 release).

As I've mentioned publicly, developing and cutting a new release from Graphite's master branch has become a personal and professional priority for me.

Just wanted to follow up the previous post with a quick update.

Brew macvim cannot allocate color