Profiling example app

WIP
OK, I understand. The app doesn't have any cpu or memory bugs... its just a LB app, but you push lots of in-memory documents into it, and do an expensive request.

If we are trying to show how to debug performance issues, or bugs, this isn't a great example, because there are no bugs or performance issues.

But, I guess it gives good graphs, so if that's the goal, all is good.

I recommend documenting in the README what load test does. In particular, the three APIs it is hitting, GET and the two POSTs. And also describe why one POST "leaks", and the other "burns CPU"... as far as I can tell from the code, both POSTs just add records to the in-memory DB, so would equally be "leaks"... and I can only assume the first POST has more complex processing in LB, which is why it burns CPU?

And what is the GET for?