ruby-grape / grape / 36052421143

100%

master: 100%

Pull #3008

github

Add the grape-on-rack app as a live-server memory profiling harness

Memory-profiling Grape under a real web server meant a separate
grape-on-rack checkout whose Gemfile pointed at a local Grape path.
benchmark/grape_on_rack brings that app here, with its own Gemfile
resolving `grape` from the repository root, so a profile always runs
against the working tree:

    ruby-memory-profiler --pretty --out=latest_cache.txt \
      --allow-files=grape/lib run -- bundle exec rackup --env none

while profile_api_calls.rb drives every mounted API from a thread pool.

The APIs and the Rack wrapper are carried over as they are. The boot
files are folded into config.ru, which compiles the API before serving.
The specs, the Swagger UI assets, New Relic and the tooling config are
left out, as none of them take part in a profile.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

1490 of 1490 branches covered (100.0%)

Branch coverage included in aggregate %.

4326 of 4326 relevant lines covered (100.0%)

29276.48 hits per line