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

Only one core used on Windows Server 2019 #124

Open
Civitello opened this issue Oct 25, 2021 · 2 comments
Open

Only one core used on Windows Server 2019 #124

Civitello opened this issue Oct 25, 2021 · 2 comments

Comments

@Civitello
Copy link

Description of issue:
When using Windows Server 2019 on c5 and c5a AWS instances, only one core is used no matter what is selected for the:
Cores (Threads) to use:
option.

Steps to reproduce:

  1. Launch an instance of Windows Server 2019 on a c5 or c5a AWS instance (other instance types not tested).
  2. Install Java Windows Offline (64-bit) from here: https://www.java.com/en/download/manual.jsp
  3. Download Sassa-v0.6.3
  4. Launch Sassa
  5. Select any Biome
  6. Set cores to max
  7. Click Start
  8. View the Performance tab of Task Manager
  9. Observe that the load on the CPU is not 100%

Expected Behaviour:
CPU load is 100%

Please feel free to reach out to me with any questions or requests for testing.

@Civitello
Copy link
Author

Did some more testing. On m5zn instances the difference in performance between 12 core and 24 core is nowhere near linear.

A task that takes
2:30 to 2:51
on a 24 core takes
~3:30
on a 12 core.

@Zodsmar
Copy link
Owner

Zodsmar commented Nov 20, 2021

So the new version that I am working on will have a CLI option, so you can run it headless. (There will be a config file assosiated with it to pass in the search parameters) I am doing a full rewrite of the code so once the 1.18 update is released can you test it again and let me know? If you still have the same problem, I will dig into it.

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