OS Name/Version:
Debian GNU/Linux 12
Product Name/Version:
Decadeus Ver. 2.4.8.0
Problem Description:
AMP is not detecting / utilizing my other physical CPU
Steps to reproduce:
Step 1 - View system specs in Support and Updates
Step 2 - Scroll down to CPU layout and see 1S/12C/24T
Actions taken to resolve so far:
None/Unsure how to fix or proceed
Unless you’re using the Docker settings to limit CPU it doesn’t affect anything aside from visual issues. You can run lscpu and share the output here and we can find out why.
Hello @IceOfWraith and thank you for your response, I am running AMP without docker enabled… please see below for the output of lscpu also I ran into another issue… I am unable to run two instances of Palworld… I get the following error steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory … would reinstalling AMP with docker enabled fix this since each container would have it’s own dependencies?
EDIT: I went ahead and installed docker & docker compose… going to test it out to see if it solves my second issue.
2nd EDIT: Docker totally solved my second issue lol… I’m an idiot for not using docker in the first place. Also wanted to note that the controller / main instance isn’t on docker so it should have access to the full system resources.
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz
CPU family: 6
Model: 45
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 2
Stepping: 7
CPU(s) scaling MHz: 57%
CPU max MHz: 2800.0000
CPU min MHz: 1200.0000
BogoMIPS: 4588.93
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bt
s rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_time
r aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 384 KiB (12 instances)
L1i: 384 KiB (12 instances)
L2: 3 MiB (12 instances)
L3: 30 MiB (2 instances)
NUMA:
NUMA node(s): 2
NUMA node0 CPU(s): 0-5,12-17
NUMA node1 CPU(s): 6-11,18-23
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: KVM: Mitigation: VMX disabled
L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Mds: Mitigation; Clear CPU buffers; SMT vulnerable
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
Can you show what AMP is displaying?
So it’s just reporting the wrong number of sockets, it seems? The core and thread counts line up from what it shows there.
I thought so too but even if it was only reporting the wrong # of sockets each CPU is 12 cores so it would say 1S/24C/48T right?
That CPU has 6 cores and 12 threads. So it seems to be correct unless I’m missing something.
Tbosw are your threads. It has 6c but 12t due to hyperthreading. 
Ah, yep… sorry lol so I guess this isn’t an issue then?
Just the socket count, which is visual only thankfully.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
