Skip to content

Conversation

@LesnyRumcajs
Copy link
Member

@LesnyRumcajs LesnyRumcajs commented Mar 21, 2025

Summary of changes

Changes introduced in this pull request:

  • first draft of Forest benchmarking with k6

Reference issue to close (if applicable)

Closes #5389

Other information and links

Change checklist

  • I have performed a self-review of my own code,
  • I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
  • I have added tests that prove my fix is effective or that my feature works (if possible),
  • I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

@LesnyRumcajs LesnyRumcajs marked this pull request as ready for review March 21, 2025 16:17
@LesnyRumcajs LesnyRumcajs requested a review from a team as a code owner March 21, 2025 16:17
@LesnyRumcajs LesnyRumcajs requested review from elmattic and lemmih and removed request for a team March 21, 2025 16:17
@@ -0,0 +1,13 @@
all-forest-cloud:
Copy link
Contributor

Choose a reason for hiding this comment

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

These commands could go into package.json. It's rare to use makefile in js world.

Copy link
Member Author

Choose a reason for hiding this comment

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

I wouldn't say we are precisely in the JS world. k6 itself is a Go app that happens to use JS for its test scenarios.


| Name | Description | Type | Default |
| --------------- | --------------------------- | ---- | ------------------------------ |
| `K6_TEST_URL` | Node RPC endpoint | URL | `http://localhost:2345/rpc/v1` |
Copy link
Contributor

@hanabi1224 hanabi1224 Mar 24, 2025

Choose a reason for hiding this comment

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

How about prefixing environment variables with FOREST_RPC_

Copy link
Member Author

Choose a reason for hiding this comment

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

A strong no. These benchmarks should be client-agnostic.

Copy link
Contributor

@hanabi1224 hanabi1224 left a comment

Choose a reason for hiding this comment

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

It'd be great to use typescript. I can do that afterwards.

@LesnyRumcajs LesnyRumcajs added this pull request to the merge queue Mar 25, 2025
Merged via the queue into main with commit 6014d9b Mar 25, 2025
41 checks passed
@LesnyRumcajs LesnyRumcajs deleted the rpc-benchmarks branch March 25, 2025 13:27
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.

Investigate k6 usage for RPC benchmarking

4 participants