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

Add CI tests for benchmarks. #2

Closed
wants to merge 700 commits into from
Closed

Add CI tests for benchmarks. #2

wants to merge 700 commits into from

Conversation

shachlanAmazon
Copy link
Owner

  1. Allow benchmarks to run in a minimal fashion, that shouldn't take a long while.
  2. Add CI task for each language, so that benchmarks will run for it.
  3. Add relevant file extensions for changes that should trigger CI for each language.

barshaul and others added 30 commits August 31, 2023 07:03
Python - config rewrite command
Throw concrete error types from node client.
Fixing Python's INFO parser to support parsing Redis 7.2 INFO output
JS might perform a lot of tests when checking if an object is truthy.
This saves the cost of allocating a new error on every promise.
Apparently this has a significant perf cost.
Removed the FFI client from the Python wrapper
barshaul and others added 29 commits November 14, 2023 11:07
* Align indentation for java .yml files.

All other .yml files use this indentation.

* Run Java's CI only on branch pushes to main.

We don't need to run CI on every push to every development branch.
These timeouts carry a significant performance penalty. Their benefit is
more precise timeouts to the user, but we're willing to be off by a bit
in order to improve perf.
This means that if you pass the `--stripInternal` flag to `tsc`, these
functions won't be emitted in the typescript declaration files, and we
won't expose the protobuf types.

temp
Added redis installation guide to node README
* Remove csharp socket client.

* C#: Use our client, not the redis-rs multiplexer.

* Use generics in MessageContainer.

This allows us to move some of the message logic to MessageContainer.

* Fix benchmark program.

* Message: Implement awaiter.

`Message` now implements GetAwaiter, which allows the TPL to await on
`Message`s, which is much more efficient, and removes the need for
`ValueTask`s. As a part of the change, now `Message`s report to their
`MessageContainer` when they complete an action, and can be made
available again. Additionally, `Message`s now can return `null` regardless
of their generic type - this is done in order to remove a warning, since
the code can't ensure that the returned value isn't `null` without
additional runtime checks, and `null` values are legal in our flows.

* re-enable csharp github actions.

* Fix compilation.

* PR comments.

* C#: Rename connection to client.

---------

Co-authored-by: nihohit <[email protected]>
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.

10 participants