@Dashrender said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @Pete-S said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @wrx7m said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @Pete-S said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @wrx7m said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @Pete-S They list both the 61xx and 62xx as options for the R740XD. Good! What CPUs do you have in the R720 today? 1 or 2 CPUs? Do you want the new ones to be faster or just capable of running more VMs? I have 2 x E5-2609 CPUs in each server. I would like faster, but more VMs would be the priority. The E5-2609 CPUs are at the low end of what was available at the time so no problem there. Actually, are you looking to keep the old servers around for testing and such? In that case you could just drop in refurbished CPUs that are faster and/or has more cores for very little money. If the server can take E5-2600 V2 you can get up to 12 core CPUs. yeah, but Windows licensing is an issue, assuming multiple CPUs... for a test server, not likely worth going over the 16 cores. Not to mention the test server might require licensing (if needed beyond the 90 day test period for something). Two 8-cores would be an option. For instance two E5-2690. They are 2.9 GHz base frequency and have 8 cores. About $100 each when buying refurbished. About 50% faster per core (2609 have no turbo) and about 3 times faster multicore performance. Has more cache and faster memory transfer speed. Was a very high end CPU at the time. Was listed at $2000 while the E5-2609 was $300. The fastest 8-core E5-2600 V2 CPU is the E5-2667 V2. 8 cores and base frequency of 3.3 GHz. It will likely also be an option for the R720XD. V2 uses 22nm technology so uses less power with the same clock speed and can fit more cores or run higher frequencies.

@NerdyDad said in Changing NICs in virtual servers: Here is the actual code in a more searchable context, sterilized for general use. Very useful! Thanks!

@obsolesce said in Linux-based StarWind VSAN: hardware-agnostic, minimalistic, and FREE SDS: @travisdh1 said in Linux-based StarWind VSAN: hardware-agnostic, minimalistic, and FREE SDS: @obsolesce said in Linux-based StarWind VSAN: hardware-agnostic, minimalistic, and FREE SDS: Is this tied together with VMWare? I thought this was going to be usable on Fedora, for example. If the Starwind software is running on Linux, the hypervisor shouldn't matter. You'll be able to mount the share Starwind it's exporting on XenServer or KVM just as well, but well all the experts just in case. @KOOLER @Oksana I'm asking because Linux and SW vSAN are worded everywhere as if it's 100% tied to VMWare, with no other use case. I can't imagine that being the case, but am asking to make sure... perhaps it's worded like that because it's written by a VMWare Architect trying to boast and sell VMWare. Just wondering, because I was under the impression you can use it how you want, not just with VMWare. I agree with you, seems like bad marketing. I’ll be interestes in using it with KVM, for example. I thing it will just export iSCSI.