https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
r
n
yes, i saw that but it didn't answer my question.
are you saying there should be a 2:1 ratio?
should it be 2 cores with a total of 3 sockets
r
For me I follow the Techzone doc for the Ring vs mesh CPU arch. Then I follow the sizing 2:1. For the Socket and cores. I do 1 socket and x amout of cores. I have not went above 1 socket and 6 cores that I can remember. @Rob Zylowski Might be able to give you a better idea. Or anyone that has some spot on formula lol.
n
i suck at calculating this stuff...i've gotten lucky so far.
does it really impact performance if i leave on 1 core per socket? it sounds like that feature was created to assist with licensing.
r
Just a question, not meant to be taken wrong. Have you read about the Numa terminology by chance?
All this can be tricky and it plays a role in cpu cores and amount of ram. https://blogs.vmware.com/performance/2017/03/virtual-machine-vcpu-and-vnuma-rightsizing-rules-of-thumb.html Check out this. Al though it’s not citrix but give a breakdown on vmuma and cores /sockets. Now intel updated the newer chips that use a mesh connection in the chip. It’s supposed to be more efficient in terms of Numa not so much being an issue. Now that’s my understanding of it and I could be wrong. Now I understand this may not be the case for RDSH/XA/XD machines. I would test out 1 socket and 6 cores.
n
@Ray Davis no, i have to read it.
i mean a read about a little bit
but that stuff confuses me
c
Last time I looked into it on ESX there wasn't any performance difference anymore, but the controls are still there because some licensing is based on cores/sockets.
s
i never adjust sockets, just doesn't really make sense to me. And i try to stick with NUMA sizes. However, most modern hypervisors don't have an issue with adjusting cores or sockets.
s
zNUMA was pretty important at one point and a lot of architects took that into consideration when designing systems. But, the impact that it had varied depending on the applications and how made use of multiple cores (think threads here and processor queue length.) Although I haven't kept up with it recently the new processors are not supposed to be NUMA bound and that, of course, will change that consideration. So, unfortuanately, @newbie1998 there's not a one-size fits all answer. A few factors you may have to consider (ie. applications running, processor family (architecture, etc.) As the typical consulting answer... "IT depends" Best advice. TEST, TEST, TEST
r
is zNuma new?
or was that v and I am reading into it to much lol
r
I think he just meant NUMA he added the z for me 🙂
r
LOL
s
I have very FAT fingers.....
r
NUMA used to matter more as there were memory boundaries but these days a NUMA node is always a single physical processor. So for Citrix VDAs we like to align with the number of cores in the VDA being a divisor of the cores in the processor to make scheduling easier on the hypervisor. so if you processor has 18 cores and your doing largish servers you might use 9 cores. Luckily processors are susually more like 24 cores which gives more options like 2,4,6,8, or 12
💯 1
2 Views
Open in Slack
PreviousNext
Powered by