for (; counter < 1_000; counter++) {
// ... I know this doesn't make much sense :)
}
I think the JVM would optimise away this loop because it doesn't do anything. e.g. if the loop optimisation method is to unroll the loop into 1000 inline statements, there's nothing there.
This makes "No Logging" result not quite a fair comparison; maybe something like the sum of 1000 random numbers do some actual work in the loop.
Exactly my thoughts when reading the article. A bad micro-benchmark that puts everything in bad context as a result. I have numbers on the impact of logging from other articles that show a significant impact, but nothing at this scale.
There is aot native compilation in javaland these days, but I assume you mean javac, the compiler that transforms source into jvm bytecode. It defers pretty much all optimization to the JITs and won't remove empty loops.
After Google Plus was released, Google changed its search syntax slightly so that you now need to "quote" mandatory terms instead of prefixing them with a + symbol.
This is pretty old now (2000-ish?) but is a pretty great graphical and interactive demonstration of how interlinked the big corporations' boardrooms are.
Check out the 'popular maps' for some good examples.
Edit: It was connected to littlesis.org in 2011 ("a free database of who-knows-who at the heights of business and government")
