Is hyper Server utilize threads? #3016
-
|
Greetings! Before tokio, hyper utilized threads: https://docs.rs/hyper/0.9.5/hyper/server/index.html
But what about now? Should I manually spawn a task for every incoming connection to utilize the whole CPU? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
If you're using If you're using The runtime (such as Tokio) will use multiplex the tasks across the amount of threads you've configured it to use (Tokio will use the same amount of threads as CPUs if you didn't specify otherwise). |
Beta Was this translation helpful? Give feedback.
-
|
That's what I meant, if you're using |
Beta Was this translation helpful? Give feedback.
-
|
Great! Thanks! |
Beta Was this translation helpful? Give feedback.
-
Okey, then I miss something. For example there will no futures connections until wait complete: P.S. By this wait I emulate TLS handshake then try connect to TLS but by http protocol. use hyper::{
server::{accept, Server},
service::{make_service_fn, service_fn},
Body, Request, Response,
};
use std::{
convert::Infallible,
net::SocketAddr,
sync::atomic::{AtomicUsize, Ordering},
time::Duration,
};
use tokio::net::TcpListener;
use tokio_stream::wrappers::TcpListenerStream;
use tokio_stream::StreamExt;
#[tokio::main]
async fn main() {
static RCX: AtomicUsize = AtomicUsize::new(0);
let addr = SocketAddr::from(([127, 0, 0, 1], 3000));
let listener = TcpListener::bind(addr).await.unwrap();
let stream = TcpListenerStream::new(listener).then(|stream| async move {
if RCX.fetch_add(1, Ordering::SeqCst) % 2 == 0 {
println!("wait");
// there can be TLS handshake
tokio::time::sleep(Duration::from_secs(10)).await;
} else {
println!("no wait");
}
stream
});
let incoming = accept::from_stream(stream);
Server::builder(incoming)
.serve(make_service_fn(|_conn| async {
Ok::<_, Infallible>(service_fn(|req: Request<Body>| async move {
Ok::<_, Infallible>(Response::new(Body::from(format!("{req:?}"))))
}))
}))
.await
.unwrap()
} |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there is a shortcoming in v0.14.x, that the accept handshake part is done in the same task. Once a connection is accepted, it's spawned into a new task. You can either make the |
Beta Was this translation helpful? Give feedback.
-
Any issue for this? |
Beta Was this translation helpful? Give feedback.
If you're using
hyper::Server, it will spawn a task for each connection.If you're using
hyper::server::conn::Httpcombined with your own socket listener, then you could spawn each HTTP connection into a task.The runtime (such as Tokio) will use multiplex the tasks across the amount of threads you've configured it to use (Tokio will use the same amount of threads as CPUs if you didn't specify otherwise).