fix(runtime): remove forcing tokio core count to 2

rivet-gg · Feb 27, 2025 · 1a6660e · 1a6660e
1 parent 65091d6
commit 1a6660e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 10 deletions.
diff --git a/packages/common/chirp/perf/src/ctx.rs b/packages/common/chirp/perf/src/ctx.rs
@@ -202,7 +202,7 @@ impl PerfCtxInner {
 						.await
 						.push(PerfMark::new(base_ts, label, None, None));
 				}
-				.instrument(tracing::info_span!("perf_mark_async")),
+				.instrument(tracing::trace_span!("perf_mark_async")),
 			);
 		if let Err(err) = spawn_res {
 			tracing::error!(?err, "failed to spawn perf_mark_async task");
@@ -237,7 +237,7 @@ impl PerfCtxInner {
 						Some(req_id),
 					));
 				}
-				.instrument(tracing::info_span!("perf_mark_rpc_async")),
+				.instrument(tracing::trace_span!("perf_mark_rpc_async")),
 			);
 		if let Err(err) = spawn_res {
 			tracing::error!(?err, "failed to spawn perf_mark_rpc_async task");

diff --git a/packages/common/runtime/src/lib.rs b/packages/common/runtime/src/lib.rs
@@ -38,14 +38,6 @@ fn build_tokio_runtime_builder() -> tokio::runtime::Builder {
 
 	if let Ok(worker_threads) = env::var("TOKIO_WORKER_THREADS") {
 		rt_builder.worker_threads(worker_threads.parse().unwrap());
-	} else {
-		// Default to 2 threads since this is likely running in a shared
-		// context. If we constrain this task to use 100 MHz an 8 core system,
-		// it will still spawn 8 threads needlessly.
-		//
-		// If a service is configured to use a dedicated core, Bolt will expose
-		// the correct thread count.
-		rt_builder.worker_threads(2);
 	}
 
 	if let Ok(max_blocking_threads) = env::var("TOKIO_MAX_BLOCKING_THREADS") {