New test with a focus on server response and templating engine rendering

[ruroru]

I would like to suggest a new test type, which would focus on the server response + template rendering, similar to how it is done in Fortunes test. But unlike in fortunes the database will not be queried on every request, but instead once (when the server starts for example). The advantage of having this setup is that frameworks can 100% focus on request and render and they will not be throttle by database connections. On top of it, there are quite a few frameworks in Fortune whose performance is "underwhelming" mainly because the wrong or incorrect or not optimal connection or pool setup.

The sequence diagram could look like

sequenceDiagram
   participant C as Client
   participant S as Server
   participant DB as Database
   participant TE as TemplatingEngine

   Note over S: Cache template context
   S->>+DB: Query context
   DB-->>-S: Context

   C->>+S: HTTP Request
   S->>+TE: Render(template, context)
   Note right of TE: Templating engine renders HTML
   TE-->>-S: HTML Output
   S-->>-C: HTTP Response

[joanhey]

First, any app that don't use the database, is almost a useless app !! or we are using proxies, and this bench is not for that.

Later, the 800 fw implementations need to change or add a new test 😛

Try it, but I think is difficult, when similar tests measure the same factors.