Skip to content
Discussion options

You must be logged in to vote

The conclusions drawn from a week of stress testing:

  1. Tokio's asynchronous operations are not unlimited; when concurrency is high and individual tasks take significant time to complete, it can lead to blocking, making it suitable only for handling short and fast requests.
  2. CPU-intensive tasks may not be well-suited for the Axum framework.
  3. Services involving CPU computations can perform up to 10 times worse in containers compared to bare-metal environments.

thanks.

Replies: 2 comments 11 replies

Comment options

You must be logged in to vote
10 replies
@lijingrs
Comment options

@mladedav
Comment options

@lijingrs
Comment options

@lijingrs
Comment options

Answer selected by lijingrs
Comment options

You must be logged in to vote
1 reply
@lijingrs
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants