Generate configuration cache before starting benchmarks

Symfony relies on configuration caching to avoid booting the whole system on every request over and over again. If you are not doing this during the build process, then the application might run into cache slams during the first 2-3 second when the cache is generated the first time.

Compared to lightweight frameworks such as Laravel or Silex, Symfony uses lots of configuration files that are parsed and compiled into two php files (one for the services, one for the routing). This is comparable to the compile step of any static language and only done once. It is not a runtime cache.
Update setup.py

Fix typo
Update setup.py

Fix arguments to subprocess.call
Add '-raw' for Flask (uses SQLAlchemy core for connection pooling
but not the ORM.

Tweak the single query code slightly for both normal (ORM) and
raw (non-ORM)
ignore hsenv & cabal-dev
yesod mongodb implementation
add mongodb-raw for yesod
benchmark_config more similar to nodejs
WAI implementation for json
fix yesod README
only run the raw version of the mongoDB benchmarks
Fortune testcase for Symfony 2
fix yesod mongodb-raw test
Changed the db config. It's possible ...

... to change the number of connections per node and the
ExecutionContext now.
go: Remove manual pooling. Add parallel ops. Depends on https://codereview.appspot.com/8836045/.
go: Touch code style.
go: Remove charset request, up connection count from 80 to 100.
Compojure: Add "raw" test
fix benchmark_config commas
Fortune testcase for Laravel