Skip to content

Conversation

@rafaelfranca
Copy link
Collaborator

We want to track the performance of common operations in the Addressable gem, such as parsing, normalization, component access, and modification.

We heavily use the Addressable gem in our projects, so having benchmarks will help us monitor performance changes over time and ensure that updates to the gem or our codebase do not introduce regressions.

We want to track the performance of common operations in the Addressable gem,
such as parsing, normalization, component access, and modification.

We heavily use the Addressable gem in our projects, so having benchmarks will help
us monitor performance changes over time and ensure that updates to the gem or our
codebase do not introduce regressions.
@rafaelfranca rafaelfranca requested a review from a team November 15, 2025 00:02
public_suffix (6.0.2)

PLATFORMS
aarch64-linux
Copy link
Member

Choose a reason for hiding this comment

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

I guess that's more of a Bundler thing/issue, but I wonder why the architecture is even included here given those are pure-Ruby gems.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

AFAIK, that is the default behavior of bundler. It always include the architecture where the gemfile was created

@tekknolagi tekknolagi enabled auto-merge (squash) November 17, 2025 22:47
@tekknolagi tekknolagi merged commit bcc821a into main Nov 17, 2025
3 checks passed
@tekknolagi tekknolagi deleted the rmf-add-benchmark branch November 17, 2025 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants