Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use all cores in ue4 build #40

Closed
ki11roy opened this issue Jun 4, 2019 · 4 comments
Closed

Use all cores in ue4 build #40

ki11roy opened this issue Jun 4, 2019 · 4 comments

Comments

@ki11roy
Copy link

ki11roy commented Jun 4, 2019

How to use all the cores in ue4 build? It seems that it uses only two by default:

12:57:00]	[Step 2/3] Reflection code generated for juydEditor in 15.2554895 seconds
[12:57:02]	[Step 2/3] Using Visual Studio 2017 14.16.27023 toolchain (C:\BuildTools\VC\Tools\MSVC\14.16.27023) and Windows 10.0.17763.0 SDK (C:\Program Files (x86)\Windows Kits\10).
[12:57:02]	[Step 2/3] Building 31 actions with 2 processes...
@adamrehn
Copy link
Owner

adamrehn commented Jun 5, 2019

Under Windows hosts, process isolation mode will use all available CPU cores, whereas VMs spawned by Hyper-V isolation mode only have access to two CPU cores by default. Are you using process isolation mode or Hyper-V isolation mode?

@ki11roy
Copy link
Author

ki11roy commented Jun 5, 2019

Correct, I am in Hyper-V mode.

@adamrehn
Copy link
Owner

adamrehn commented Jun 5, 2019

In that case the behaviour you're seeing is expected. For maximum performance I would recommend using process isolation mode if possible, since Hyper-V isolation mode suffers from a number of issues in addition to the CPU core limit that make it poorly suited to building large, complex container images such as those produced by ue4-docker. Process isolation mode will be used by default if you're running the latest version of ue4-docker with Docker 18.09 under Windows 10 version 1809 or newer.

@adamrehn adamrehn closed this as completed Jun 5, 2019
@ki11roy
Copy link
Author

ki11roy commented Jun 5, 2019

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants