Adding execution time measurement facility

[vershov]

This is regarding issue #918

[woodbri]

@vershov FYI, you should make your pull requests off the development branch. Also you might consider adding cucumber test(s) as these are often requested.

BTW, this is a nice feature. Thanks!

[vershov]

@woodbri Thanks for the comment.
I have check the test suite and find three main topics to test: node maps, lat/lon tests, and routability tables. The feature I proposed is auxiliary feature and should not be invoked at real requests. It's primarily for performing server load/capacity testing. So, I suppose we could leave the current suite as is and does not expand with new functionality re this small feature.

[DennisOSRM]

@vershov Thanks for the PR.

a couple of remarks:

• As @woodbri said, make your pull requests off develop branch.
• Util/TimeMeasurement.h is a duplicate to TimingUtil.h
• The API name measurement is somewhat ambiguous
• check indentation. we use four spaces
• std::find_if(.) is too expensive to use at this point as it takes time linear in the size of the string

[emiltin]

i don't agree that we should not test this.

[DennisOSRM]

I second @emiltin 's opinion. Ideally, every single feature gets tested. Even if it is a small one.

[emiltin]

the helpers available for testing let/lon, routability, etc, are just helpers. in case we need to test others features, other helpers can be added.

[DennisOSRM]

Closing here in favor of #922