-
Notifications
You must be signed in to change notification settings - Fork 64
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
How about the multi-core support of stand-alone dual-socket motherboards? #19
Comments
Hello @win10ogod! I've never worked with dual-socket motherboards. How are these processors visible in the system? If the system can synchronize threads of one application on two processors without any special adjustments, it should work with no problem. If not, you can create two pods/dockers assigned to each processor, then connect Distributed Llama inisde these containers via a local network. |
@b4rtaz Dual-socket mbs are usually present CPUs as 2 (or more if CPUs themselves are high-core-count) NUMA nodes. This sometimes configure in BIOS (look for Cluster-on-Die and like options). I do have dualsocket MB with 2 Xeon E5 2680 v4. Got MB and CPUs rather cheap from aliexpress. 28 cores / 56 threads. I use it as proxmox node with 220 Gb RAM(would be 256 when I replace 8th DIMM). |
I'm actually curious here, say you do have two VM's on the same machine and both have a CPU dedicated for it, would the memory also be distributed in such a way that the memory each has access to is those that it has the fastest access to? |
@DifferentialityDevelopment hypervisor should take this into account. if you ignore all of this - it would just work but it could run slower than it possible |
How about the multi-core support of stand-alone dual-socket motherboards?
The text was updated successfully, but these errors were encountered: