pub struct Server<T: 'static + Context<Response = Response> + Clone + Send + Sync, S: 'static + Send + Sync> { /* private fields */ }
Implementations§
source§impl<T: 'static + Context<Response = Response> + Clone + Send + Sync, S: 'static + Send + Sync> Server<T, S>
impl<T: 'static + Context<Response = Response> + Clone + Send + Sync, S: 'static + Send + Sync> Server<T, S>
sourcepub fn start_work_stealing_optimized(self, host: &str, port: u16)
pub fn start_work_stealing_optimized(self, host: &str, port: u16)
Starts the app with the default tokio runtime execution model
sourcepub fn start_small_load_optimized(self, host: &str, port: u16)
pub fn start_small_load_optimized(self, host: &str, port: u16)
Starts the app with a thread pool optimized for small requests and quick timeouts. This is done internally by spawning a separate thread for each reactor core. This is valuable if all server endpoints are similar in their load, as work is divided evenly among threads. As seanmonstar points out though, this is a very specific use case and might not be useful for everyday work loads.alloc
See the discussion here for more information:
https://users.rust-lang.org/t/getting-tokio-to-match-actix-web-performance/18659/7
Trait Implementations§
Auto Trait Implementations§
impl<T, S> !RefUnwindSafe for Server<T, S>
impl<T, S> Send for Server<T, S>
impl<T, S> Sync for Server<T, S>
impl<T, S> Unpin for Server<T, S>
impl<T, S> !UnwindSafe for Server<T, S>
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more