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

Improve worker_max_blocking_threads documentation #3477

Merged
merged 4 commits into from
Oct 7, 2024

Conversation

luca-iachini
Copy link
Contributor

PR Type

Documentation

PR Checklist

  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • A changelog entry has been made for the appropriate packages.
  • Format code with the latest stable rustfmt.
  • (Team) Label with affected crates and semver status.

Overview

The current documentation for HttpServer::worker_max_blocking_threads says that the default number of blocking threads is "512 divided by the number of workers." However, this could lead someone to believe that the default value depends on the number of workers set in HttpServer, when it actually depends on the system's available_parallelism.

@robjtede robjtede added A-web project: actix-web B-semver-norelease change that does not require a release labels Oct 7, 2024
Copy link
Member

@robjtede robjtede left a comment

Choose a reason for hiding this comment

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

Nice catch, thanks 👍🏻

@robjtede robjtede added this pull request to the merge queue Oct 7, 2024
Merged via the queue into actix:master with commit 3849cda Oct 7, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-web project: actix-web B-semver-norelease change that does not require a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants