From 7f619d90519a996243430fc3b556687ae2bab6df Mon Sep 17 00:00:00 2001
From: Philip Rebohle <philip.rebohle@tu-dortmund.de>
Date: Tue, 22 May 2018 00:32:44 +0200
Subject: [PATCH] [dxvk] Use only one extra thread for async pipeline
 compilation

With the benefits of asynchronous compilation being generally low and
compilation in advance not being feasible, there is no reason to create
more threads.
---
 src/dxvk/dxvk_pipecompiler.cpp | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/src/dxvk/dxvk_pipecompiler.cpp b/src/dxvk/dxvk_pipecompiler.cpp
index 425fe723..6d41a59d 100644
--- a/src/dxvk/dxvk_pipecompiler.cpp
+++ b/src/dxvk/dxvk_pipecompiler.cpp
@@ -4,9 +4,7 @@
 namespace dxvk {
   
   DxvkPipelineCompiler::DxvkPipelineCompiler() {
-    // Use ~half the CPU cores for pipeline compilation
-    const uint32_t threadCount = std::max<uint32_t>(
-      1u, std::thread::hardware_concurrency() / 2);
+    constexpr uint32_t threadCount = 1u;
     
     Logger::debug(str::format(
       "DxvkPipelineCompiler: Using ", threadCount, " workers"));