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

♻️ Refactor: Improve Performance of getSplicedStrList #3318

Merged
merged 5 commits into from
Feb 24, 2025

Conversation

ksw2000
Copy link
Member

@ksw2000 ksw2000 commented Feb 22, 2025

Description

Improve the implementation of getSplicedStrList.

  1. The original getSplicedStrList calls utils.TrimLeft. In the new one, I integrated the trim-left functionality by tracking the leading space, without calling other functions.
  2. The original getSplicedStrList copies the dst slice when it is not large enough. I believe this operation can be handled more efficiently using golang built-in append function.
goos: linux
goarch: amd64
pkg: github.com/gofiber/fiber/v3
cpu: AMD EPYC 7763 64-Core Processor                
                           │   old.txt   │               new.txt               │
                           │   sec/op    │   sec/op     vs base                │
_Utils_GetSplicedStrList-4   66.12n ± 1%   51.05n ± 1%  -22.79% (p=0.000 n=50)

                           │  old.txt   │            new.txt             │
                           │    B/op    │    B/op     vs base            │
_Utils_GetSplicedStrList-4   0.000 ± 0%   0.000 ± 0%  ~ (p=1.000 n=50) ¹
¹ all samples are equal

                           │  old.txt   │            new.txt             │
                           │ allocs/op  │ allocs/op   vs base            │
_Utils_GetSplicedStrList-4   0.000 ± 0%   0.000 ± 0%  ~ (p=1.000 n=50) ¹
¹ all samples are equal

Type of change

Performance improvement (non-breaking change which improves efficiency)

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.

goos: linux
goarch: amd64
pkg: github.com/gofiber/fiber/v3
cpu: AMD EPYC 7763 64-Core Processor
                           │   old.txt   │               new.txt               │
                           │   sec/op    │   sec/op     vs base                │
_Utils_GetSplicedStrList-4   66.12n ± 1%   51.05n ± 1%  -22.79% (p=0.000 n=50)

                           │  old.txt   │            new.txt             │
                           │    B/op    │    B/op     vs base            │
_Utils_GetSplicedStrList-4   0.000 ± 0%   0.000 ± 0%  ~ (p=1.000 n=50) ¹
¹ all samples are equal

                           │  old.txt   │            new.txt             │
                           │ allocs/op  │ allocs/op   vs base            │
_Utils_GetSplicedStrList-4   0.000 ± 0%   0.000 ± 0%  ~ (p=1.000 n=50) ¹
¹ all samples are equal
Copy link

codecov bot commented Feb 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.25%. Comparing base (4b62d3d) to head (30bd0fe).
Report is 25 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3318      +/-   ##
==========================================
+ Coverage   84.21%   84.25%   +0.03%     
==========================================
  Files         116      116              
  Lines       11558    11554       -4     
==========================================
+ Hits         9734     9735       +1     
+ Misses       1395     1391       -4     
+ Partials      429      428       -1     
Flag Coverage Δ
unittests 84.25% <100.00%> (+0.03%) ⬆️

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.

Copy link
Contributor

coderabbitai bot commented Feb 22, 2025

Walkthrough

The pull request refactors the getSplicedStrList function in helpers.go to simplify its loop using a switch statement, reduce variable usage, and eliminate internal slice resizing. Additionally, the associated tests in helpers_test.go have been expanded with five new test cases that assess edge case scenarios involving commas and spaces, thereby improving overall test coverage without modifying any public API.

Changes

Files Summary of Changes
helpers.go Refactored getSplicedStrList: simplified loop logic with a switch statement, removed multiple variables and resizing logic, and streamlined substring appending.
helpers_test.go Added five test cases for getSplicedStrList to verify handling of leading/trailing spaces, single and multiple commas, and combinations of commas with spaces.

Sequence Diagram(s)

sequenceDiagram
    participant T as Test
    participant F as getSplicedStrList
    T->>F: Call with headerValue string
    loop Process each character
        F->>F: Evaluate character via switch
        alt Comma encountered
            F->>F: Append current substring to result
        end
    end
    F->>T: Return resulting string slice
Loading

Suggested reviewers

  • sixcolors
  • ReneWerner87
  • efectn

Poem

I'm a rabbit, hopping with glee,
Through refactored code so spry and free,
With commas split and spaces trimmed,
My little paws dance, perfectly primed,
A joyful leap in lines so bright,
Celebrating change in the coding night!
🐰💻


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8d0df28 and f31d758.

📒 Files selected for processing (1)
  • helpers.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • helpers.go
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Compare

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

@ksw2000 ksw2000 marked this pull request as ready for review February 22, 2025 10:00
@ksw2000 ksw2000 requested a review from a team as a code owner February 22, 2025 10:00
@ksw2000 ksw2000 requested review from gaby, sixcolors, ReneWerner87 and efectn and removed request for a team February 22, 2025 10:00
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: 0

🧹 Nitpick comments (1)
helpers.go (1)

326-328: Consider using more descriptive variable names.

While the code is efficient, the variable names could be more descriptive:

  • r could be start or segmentStart
  • leading could be isLeadingSpace
-r := 0
-leading := true
+segmentStart := 0
+isLeadingSpace := true
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 252a022 and 8d0df28.

📒 Files selected for processing (2)
  • helpers.go (1 hunks)
  • helpers_test.go (1 hunks)
🔇 Additional comments (2)
helpers_test.go (1)

306-325: Great addition of comprehensive test cases!

The new test cases effectively cover important edge cases for string splitting:

  • Handling spaces between words
  • Single and multiple comma scenarios
  • Combinations of commas and spaces

These tests help ensure the robustness of the refactored getSplicedStrList function.

helpers.go (1)

326-342: Excellent refactoring for improved performance and readability!

The refactored implementation:

  • Eliminates the need for utils.TrimLeft by tracking leading spaces directly
  • Reduces memory allocations by using string slicing
  • Improves readability with a clear switch-based state machine
  • Matches the reported 22.79% performance improvement

The PR objectives are well met with this implementation.

@ksw2000
Copy link
Member Author

ksw2000 commented Feb 22, 2025

I'm not sure whether the failed test was caused by my changes or not.

@ReneWerner87 Could you help verify this?

image

@ReneWerner87
Copy link
Member

I'm not sure whether the failed test was caused by my changes or not.

@ReneWerner87 Could you help verify this?

image

the run was really flaky, its not related to your changes

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

@ReneWerner87 ReneWerner87 added this to the v3 milestone Feb 24, 2025
@ReneWerner87 ReneWerner87 merged commit 0d1ade4 into gofiber:main Feb 24, 2025
13 of 14 checks passed
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.

3 participants