WIP: Refactor HTTP API #27
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactor HTTP GET/PUT API to try and improve efficiency.
Using the general_api _perf test, profiling a node handling all HTTP requests, prior to the change the profile was like:
After this refactor:
In theory the refactoring as removed the biggest cause of CPU use in the HTTP API - lower-casing strings. This is supported in the profile.
the refactoring reduces the number of repeated string lowerings, and across the board stops using deprecated string functions