Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🩹 Fix: Optimize Cache middleware handler #3031

Merged
merged 3 commits into from
Jun 12, 2024

Conversation

orvillesimba
Copy link
Contributor

@orvillesimba orvillesimba commented Jun 11, 2024

Description

This PR optimize cache middleware's performace, with the following changes:

  • Use Go's slices.Contains to replace original for loop (This should not increase performance but only reduce code)
  • Use strings.Builder for concat strings for key
  • requestMethod := c.Method() to avoid call Method() multiple times

Benchmark:

before

Running tool: /usr/local/go/bin/go test -benchmem -run=^$ -bench ^Benchmark_Cache$ github.com/gofiber/fiber/v3/middleware/cache

goos: linux
goarch: amd64
pkg: github.com/gofiber/fiber/v3/middleware/cache
cpu: AMD Ryzen 7 PRO 5850U with Radeon Graphics
=== RUN   Benchmark_Cache
Benchmark_Cache
Benchmark_Cache-16       4430882               271.5 ns/op            16 B/op          2 allocs/op
PASS
ok      github.com/gofiber/fiber/v3/middleware/cache    1.485s

after

Running tool: /usr/local/go/bin/go test -benchmem -run=^$ -bench ^Benchmark_Cache$ github.com/gofiber/fiber/v3/middleware/cache

goos: linux
goarch: amd64
pkg: github.com/gofiber/fiber/v3/middleware/cache
cpu: AMD Ryzen 7 PRO 5850U with Radeon Graphics
=== RUN   Benchmark_Cache
Benchmark_Cache
Benchmark_Cache-16       3884007               303.4 ns/op            32 B/op          3 allocs/op
PASS
ok      github.com/gofiber/fiber/v3/middleware/cache    1.498s

Changes introduced

List the new features or adjustments introduced in this pull request. Provide details on benchmarks, documentation updates, changelog entries, and if applicable, the migration guide.

  • Benchmarks: Describe any performance benchmarks and improvements related to the changes.
  • Documentation Update: Detail the updates made to the documentation and links to the changed files.
  • Changelog/What's New: Include a summary of the additions for the upcoming release notes.
  • Migration Guide: If necessary, provide a guide or steps for users to migrate their existing code to accommodate these changes.
  • API Alignment with Express: Explain how the changes align with the Express API.
  • API Longevity: Discuss the steps taken to ensure that the new or updated APIs are consistent and not prone to breaking changes.
  • Examples: Provide examples demonstrating the new features or changes in action.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • Enhancement (improvement to existing features and functionality)
  • Documentation update (changes to documentation)
  • Performance improvement (non-breaking change which improves efficiency)
  • Code consistency (non-breaking change which improves code reliability and robustness)

Checklist

Before you submit your pull request, please make sure you meet these requirements:

  • Followed the inspiration of the Express.js framework for new functionalities, making them similar in usage.
  • Conducted a self-review of the code and provided comments for complex or critical parts.
  • Updated the documentation in the /docs/ directory for Fiber's documentation.
  • Added or updated unit tests to validate the effectiveness of the changes or new features.
  • Ensured that new and existing unit tests pass locally with the changes.
  • Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
  • Aimed for optimal performance with minimal allocations in the new code.
  • Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Please use emojis in commit messages for an easy way to identify the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md

@orvillesimba orvillesimba requested a review from a team as a code owner June 11, 2024 03:25
@orvillesimba orvillesimba requested review from gaby, sixcolors, ReneWerner87 and efectn and removed request for a team June 11, 2024 03:25
Copy link

welcome bot commented Jun 11, 2024

Thanks for opening this pull request! 🎉 Please check out our contributing guidelines. If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

Copy link
Contributor

coderabbitai bot commented Jun 11, 2024

Walkthrough

The recent changes in middleware/cache/cache.go enhance the caching mechanism by utilizing the slices.Contains function for method checking and optimizing cache key construction with strings.Builder. These improvements streamline the code and boost performance.

Changes

Files Change Summary
middleware/cache/cache.go Modified method caching by using slices.Contains for checking request methods and optimized cache key construction using strings.Builder.

Poem

In the code where caches gleam,
We’ve made it faster, like a dream.
With slices.Contains, methods are checked,
And strings.Builder keeps keys perfect.
Efficiency now reigns supreme,
Our cache flows smooth, like a stream.
🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e561026 and c5cc690.

Files selected for processing (1)
  • middleware/cache/cache.go (2 hunks)
Additional context used
golangci-lint
middleware/cache/cache.go

[warning] 109-109: unhandled-error: Unhandled error in call to function strings.Builder.WriteString (revive)


[warning] 110-110: unhandled-error: Unhandled error in call to function strings.Builder.WriteString (revive)


[warning] 111-111: unhandled-error: Unhandled error in call to function strings.Builder.WriteString (revive)

Additional comments not posted (2)
middleware/cache/cache.go (2)

99-99: Optimization by caching the request method.

Caching the result of c.Method() in requestMethod is a good practice to avoid redundant method calls, especially in performance-critical middleware.


102-102: Use of slices.Contains for method checking.

Replacing manual iteration with slices.Contains simplifies the code and potentially improves performance by leveraging optimized library functions.

middleware/cache/cache.go Outdated Show resolved Hide resolved
@ReneWerner87
Copy link
Member

@orvillesimba can you please make another benchmark and post before and after

in the upper one the numbers have gotten worse
it has increased from 2 to 3 allocations and the time from 271ns to 303ns

@orvillesimba
Copy link
Contributor Author

@orvillesimba can you please make another benchmark and post before and after

in the upper one the numbers have gotten worse it has increased from 2 to 3 allocations and the time from 271ns to 303ns

Whoops, sorry I've mistaken ns/op, I've reverted using strings.Builder at b747a49, now changes before:

Running tool: /usr/local/go/bin/go test -benchmem -run=^$ -bench ^Benchmark_Cache$ github.com/gofiber/fiber/v3/middleware/cache

goos: linux
goarch: amd64
pkg: github.com/gofiber/fiber/v3/middleware/cache
cpu: AMD Ryzen 7 PRO 5850U with Radeon Graphics
=== RUN   Benchmark_Cache
Benchmark_Cache
Benchmark_Cache-16       4318839               276.6 ns/op            16 B/op          2 allocs/op
PASS
ok      github.com/gofiber/fiber/v3/middleware/cache    1.484s

After changes:

Running tool: /usr/local/go/bin/go test -benchmem -run=^$ -bench ^Benchmark_Cache$ github.com/gofiber/fiber/v3/middleware/cache

goos: linux
goarch: amd64
pkg: github.com/gofiber/fiber/v3/middleware/cache
cpu: AMD Ryzen 7 PRO 5850U with Radeon Graphics
=== RUN   Benchmark_Cache
Benchmark_Cache
Benchmark_Cache-16       4531694               263.5 ns/op            16 B/op          2 allocs/op
PASS
ok      github.com/gofiber/fiber/v3/middleware/cache    1.470s

Now we only benefit from "requestMethod := c.Method() to avoid call Method() multiple times" 😅

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c5cc690 and b747a49.

Files selected for processing (1)
  • middleware/cache/cache.go (2 hunks)
Additional context used
golangci-lint
Additional comments not posted (2)
middleware/cache/cache.go (2)

99-102: Optimization using slices.Contains for method checking.

This change simplifies the method check and potentially improves performance by using Go's optimized slice operations. Good use of modern Go features!


99-109: Performance concerns with the new changes.

The benchmark results indicate an increase in execution time and memory allocations. While the code optimizations are beneficial, the performance impact should be reconsidered. It might be useful to explore why the new approach increases resource usage and whether there are ways to mitigate this.

middleware/cache/cache.go Show resolved Hide resolved
Copy link

codecov bot commented Jun 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.78%. Comparing base (46fffe4) to head (16f7c0a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3031      +/-   ##
==========================================
- Coverage   82.86%   82.78%   -0.08%     
==========================================
  Files         115      115              
  Lines        8230     8227       -3     
==========================================
- Hits         6820     6811       -9     
- Misses       1082     1086       +4     
- Partials      328      330       +2     
Flag Coverage Δ
unittests 82.78% <100.00%> (-0.08%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gaby gaby changed the title 🩹 Fix: Optimize cache handler 🩹 Fix: Optimize Cache middleware handler Jun 11, 2024
Copy link
Member

@gaby gaby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@sixcolors sixcolors left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

~/Documents/GitHub/fiber (main*) » benchstat before.txt after.txt                                                                                                                                                      sixcolors@Jason-McNeils-Mac-Pro-Monterey
goos: darwin
goarch: amd64
pkg: github.com/gofiber/fiber/v3/middleware/cache
cpu: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
          │ before.txt  │             after.txt              │
          │   sec/op    │   sec/op     vs base               │
_Cache-24   550.7n ± 1%   545.8n ± 1%  -0.89% (p=0.034 n=10)

          │ before.txt │           after.txt            │
          │    B/op    │    B/op     vs base            │
_Cache-24   16.00 ± 0%   16.00 ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

          │ before.txt │           after.txt            │
          │ allocs/op  │ allocs/op   vs base            │
_Cache-24   2.000 ± 0%   2.000 ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

@ReneWerner87 ReneWerner87 merged commit 23bcbd3 into gofiber:main Jun 12, 2024
14 of 15 checks passed
@orvillesimba
Copy link
Contributor Author

🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants