benchmark

Learn how to benchmark. Amazing what else you'll learn.

The benchmark score of the processor is the highest Apple has so far. The S3 beats the pants off the iPhone 5?

One of the best ways to deep dive is to benchmark. The milliseconds gained will be a byproduct.

This change may help other operations, but probably not as much as the GC benchmark in question.

Arm's A15 allegedly has a TDP of ~4W, but if you actually benchmark the parts, you'll find that the TDPs aren't measured the same way. A15 uses a ton of power under load, just like Haswell will [5].

If there is no reaction that is a good benchmark, they don't have to stop and do anything. They could even push the envelope further and probably not get an real repercussions.

The point in the article about haskell being "too clever for this benchmark" sums up haskell generally in my experience.

If you start out with basic ORM models, benchmark your database, and add some raw SQL as you scale, you can get reasonable rcesults with ActiveRecord. If it breaks down for 100% of projects, you either have a weird definition of "breaks down", or you're doing it wrong.

Here's a benchmark for you: I am a software developer, who lobbied my congressman about patent law earlier this month, and on the day this lawsuit was filed, I was 45 minutes from the court by car. I am the textbook case of a person who would be following this story.

That these issues made it to the FTC in three weeks is probably a remarkable benchmark. As Arash did several weeks ago, wrt to the password and key issue, you seem to miss the point and almost intentionally dismiss the issue by detailing it as "old issues."

In the third page they benchmark asm. js and native with multithreading and SSE enabled. It shows upto 50x slowdown! Not exactly sure what the point of a benchmark without multithreading is.

Sure, writing your own very specific benchmark you can show us writing poorly, but we've never worked with a customer that's needed single threaded, synchronous writes to shine. If this is your use case, unless you need substantial read performance, MemSQL is not the database for you.

> The benchmark premptively runs the fans and pauses between runs in order to cool off. These measures give JRuby at least a 25% speed gain. However, JRuby still might be running slower than it would on a box with appropriate cooling. Right. Your computer can't be trusted to not throttle its performance due to crap cooling, and you're trying to benchmark using it?

> Benchmarks I couldn't find the benchmark code in the github repo, so it's hard to say what they may be measuring here. FlatBuffers presumably shares Cap'n Proto's property that encodes and decodes take zero time, which makes it hard to create a meaningful benchmark in the first place.