Skip to content

Correct the throughput numbers #5562

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.

Sign up for GitHub

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

Merged
Aaronontheweb merged 1 commit into from
Feb 3, 2022
Merged

Correct the throughput numbers #5562

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/articles/actors/dispatchers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ This is the configuration for the [*default-fork-join-dispatcher*](#built-in-dis
```hocon
default-fork-join-dispatcher {
type = ForkJoinDispatcher
throughput = 100
throughput = 30
dedicated-thread-pool {
thread-count = 3
deadlock-timeout = 3s
Expand Down Expand Up @@ -227,7 +227,7 @@ This will enable the `ChannelExecutor` to run everywhere and all Akka.NET loads,
The following configuration keys are available for any dispatcher configuration:

* `type` - (Required) The type of dispatcher to be used: `Dispatcher`, `TaskDispatcher`, `PinnedDispatcher`, `ForkJoinDispatcher` or `SynchronizedDispatcher`.
* `throughput` - (Required) The maximum # of messages processed each time the actor is activated. Most dispatchers default to `100`.
* `throughput` - (Required) The maximum # of messages processed each time the actor is activated. Most dispatchers default to `30`.
* `throughput-deadline-time` - The maximum amount of time to process messages when the actor is activated, or `0` for no limit. The default is `0`.

> [!NOTE]
Expand Down