Akka.NET v1.4.25 Release #5275
Merged
Akka.NET v1.4.25 Release #5275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* introduced new project for Akka.Cluster.Benchmarks * added first set of sharding performance specs * fixed local benchmark * completed entity routing benchmarks * added spawn entities benchmark * added SpawnEntities benchmark * fixed spawn benchmarks
Bumps [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest) from 16.10.0 to 16.11.0. - [Release notes](https://github.com/microsoft/vstest/releases) - [Commits](microsoft/vstest@v16.10.0...v16.11.0) --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Aaron Stannard <aaron@petabridge.com>
Bumps `FsCheckVersion` from 2.15.3 to 2.16.0. Updates `FsCheck` from 2.15.3 to 2.16.0 - [Release notes](https://github.com/fsharp/FsCheck/releases) - [Changelog](https://github.com/fscheck/FsCheck/blob/master/FsCheck%20Release%20Notes.md) - [Commits](fscheck/FsCheck@2.15.3...2.16.0) Updates `FsCheck.Xunit` from 2.15.3 to 2.16.0 - [Release notes](https://github.com/fsharp/FsCheck/releases) - [Changelog](https://github.com/fscheck/FsCheck/blob/master/FsCheck%20Release%20Notes.md) - [Commits](fscheck/FsCheck@2.15.3...2.16.0) --- updated-dependencies: - dependency-name: FsCheck dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: FsCheck.Xunit dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…a/akka#30328) (#5227) * this saves at least 2 seconds where the coordinator is not able to respond when the oldest node is shutdown
There was missing last curly bracket.
Co-authored-by: Aaron Stannard <aaron@petabridge.com>
…oxy (#5232) * Benchmark to test SingleRequestResponseToRemoteEntity with a local proxy * re-enable benchmark SingleRequestResponseToLocalEntity Co-authored-by: Carl Camilleri <carl.camilleri@cs-technologies.net> Co-authored-by: Aaron Stannard <aaron@petabridge.com>
If there were a major issue with the batching journals since v1.4.19, it would have been reported by now.
…ingLogic instead (#5237) Co-authored-by: Aaron Stannard <aaron@petabridge.com>
designed to help measure how quickly we can resolve a temporary actor upon deserialization
* improveme child lookup performance * modified `IActorRef.Child` API to accept a `IReadOnlyList<T>` instead of `IEnumerable<T>` * fixed a bug with low-level resolution * approved core API changes * approved again.... * fixed - was missing one approval * added extension method to simplify copying * cleaned up RepointableActorRef * cleaned up branching * implemented CopyTo method for debugging * added child-resolve program * removed expensive allocation from `MinimalActorRef.GetChild` * Revert "added child-resolve program" This reverts commit 8cce9b7. * fixed indexer operation * simplified branching inside `TryGetSingleChild` * removed redundant TryOut methods
* Ask should push unhandled answers into deadletter * update future handler * fix unit test * remove not needed return * remove redundant sync lock * remove redudant code and seal class * update api spec * update api spec 2 * handle of Status.Failure
The `AwaitAssert` is actually what made this spec racy
…PersistenceIds_publisher_when_the_last_subscriber_left (#5257) Not a good test - tightly couples to private implementation details for a given journal, plus it's racy. Better to test the stream stage it uses directly or use Akka.Streams completion semantics to check.
Bumps `FsCheckVersion` from 2.16.0 to 2.16.3. Updates `FsCheck` from 2.16.0 to 2.16.3 - [Release notes](https://github.com/fsharp/FsCheck/releases) - [Changelog](https://github.com/fscheck/FsCheck/blob/master/FsCheck%20Release%20Notes.md) - [Commits](fscheck/FsCheck@2.16.0...2.16.3) Updates `FsCheck.Xunit` from 2.16.0 to 2.16.3 - [Release notes](https://github.com/fsharp/FsCheck/releases) - [Changelog](https://github.com/fscheck/FsCheck/blob/master/FsCheck%20Release%20Notes.md) - [Commits](fscheck/FsCheck@2.16.0...2.16.3) --- updated-dependencies: - dependency-name: FsCheck dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: FsCheck.Xunit dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Same issue as in #5262
Timings were too closely fitted with the timers programmed inside the `TestStage` - added margins to allow for less-than-perfect clock resolution.
second stab at this - just don't re-use the actor's name and decouple the PersistentId from it.
Removing yet another problematic `ExpectNoMsgs` call....
* harden `ClusterShardingLeavingSpec` adding debug logging to `ClusterShardingLeavingSpec` * added more debug logging * fixed logging bug inside `ShardRegion. SendGracefulShutdownToCoordinatorIfInProgress` * fixed KV deconstruction * deprecated custom AsyncWriteProxy `Ask` implementation * allow all nodes to join at once and start sharding system right away * remove `FuturesEx`
Accidentally shared a database with the "all events by tag" query, which caused the spec to have a dirty read
so the `PipeTo` _can_ be delayed because it's running inside the `ActorTaskScheduler`, which also schedules the `Task.Delay` below.
* Ask should push unhandled answers into deadletter * update future handler * fix unit test * remove not needed return * remove redundant sync lock * remove redudant code and seal class * update api spec * update api spec 2 * handle of Status.Failure * ask should fail on system messages
…atten (#5260) * Fix Dns.Resolve issue by using ContinueWith and AggregateException.Flatten * Capture Sender as a local variable to scope it to local Co-authored-by: Aaron Stannard <aaron@petabridge.com>
…nce (#5228) * experimenting with RemoteActorRefProvider address resolution performance * implemented suggestions * fixed `Address.==` and `Address.!=` * fixed operators and generic equals * cleaned up `Address.==` * fixed `Address.==`
…system lifecycle (#5251) * Make sure stdout-loglevel setting is honored through the whole actor system lifecycle * Add settings spec for the new StandardOutLogger setting * Update API Approver list * Test logger can still output logs * Suppress LoggerInitialized from deadletter * Update API Approver list * Remove LogLevel.OffLevel for backward compatibility * Update API Approver list * Re-add OffLogLevel private const * Fix XML doc and previously hardwired StandardOutLogger type checking. * Add documentation to the new MinimalLogger implementation * Change equality to inheritance check * Add MinimalLogger spec Co-authored-by: Aaron Stannard <aaron@petabridge.com>
* stubbed out v1.4.25 release notes * completed v1.4.25 release notes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1.4.25 September 08 2021
Maintenance Release for Akka.NET 1.4
Akka.NET v1.4.25 includes some significant performance improvements for Akka.Remote and a number of important bug fixes and improvements.
Bug Fixes and Improvements
stdout-loglevel = offall the way through ActorSystem lifecycleAskshould push unhandled answers into deadletterIActorRef.ChildAPI - signficantly improves performance of many Akka.NET functions, but includes a public API change onIActorRefthat is source compatible but not necessarily binary-compatible.IActorRef GetChild(System.Collections.Generic.IEnumerable<string> name)is nowIActorRef GetChild(System.Collections.Generic.IReadOnlyList<string> name). This API is almost never called directly by user code (it's almost always called via the internals of theActorSystemwhen resolvingActorSelections or remote messages) so this change should be safe.IsNobodythrows NREExitingmembers in Read/WriteMajorityPlusPerformance Improvements
Using our standard
RemotePingPongbenchmark, the difference between v1.4.24 and v1.4.24 is significant:v1.4.24
v1.4.25
This represents a 24% overall throughput improvement in Akka.Remote across the board. We have additional PRs staged that should get aggregate performance improvements above 40% for Akka.Remote over v1.4.24 but they didn't make it into the Akka.NET v1.4.25 release.
You can see the full set of changes introduced in Akka.NET v1.4.25 here