Your question: so what?
The answer: Solar is more responsive than the other frameworks as measured in this benchmark.

Measuring a complete application (which would be different from measuring a framework) would be impossible and yield uncomparable results, especially since Solar does not endorse/force any specific scheme for database access yet (which for most frameworks is the bottleneck in an application).

One approach to measure theoretical “real world” performance would be splitting out the ORM systems and compare those, splitting out the template/view systems and compare those, and (guess what’s next) benchmark the bare bone frameworks (request handling and dispatching) themselves (like Paul did). The sum of these could possibly indicate which framework would be faster. And that’s not even considering scaling issues!

If someone demands a responsive framework, the best choice based on Pauls benchmark would be Solar. I don’t see anything wrong with that. However basing the choice of framework only on a single narrow benchmark is a stupid act and this responsibility couldn’t possibly be attributed to Paul for publishing his benchmark results.

Dangerous benchmarks? Nah, only dangerous decision makers.

Question: How did Paul benchmark the “current state of framework request dispatch responsiveness”?
Answer: With a “hello world”-app.

It is still a test of the response-time of the framework serving a single static page. Yes it shows, that one framework servs a static page faster than another one. But my question still is: So what? No one uses a framework to serve a single static page. If u want to test frameworks use a “real app” with database connections and.. and.. and..

The reason I think, why such benchmarks are a little “dangerous” is: Many not much experienced developers read such benchmarks and think… “hey this one ist the fastest – cool its the best”. (Just read the replys to the numerous benchmarks on the web).
I dont want to prevent anyone frome making his decisions based on such benchmarks – but I want to tell them, that this would be a mistake.

Paul didn’t create a starting point for benchmarks (even though that may be a side effect). He benchmarked the current state of framework request dispatch responsiveness at that time. That’s all there is to it.

There’s no need to understand the “point” of benchmarking an hello world app — because he didn’t benchmark an hello world app!

The overheads are not worth for every projects/software.

I pretty much have to agree with Lukas.
I dont really understand the intention behind a “hello world” test with fully, featured application frameworks.

Frameworks are only usefull for applications which do a little more, than printing out static pages. And this was pretty much M. Zaninottos point – that no one should judge a framework based on a “hello world” benchmark – and there I absolutly agree.

…