Skip to main content

LRDIMM or RDIMM on ESXi hosts?

Today my co-worker asked me a question about memory spec on ESXi hosts. There are two types of memory, LRDIMM and RDIMM available on hardware vendor's list. Which one is best choice?



中文版

My understanding is performance of both DIMMs are similar. The only different is capacity. LRDIMM supports higher memory density that RDIMM may not support.

If you regular server refresh plan that you never expand existing hardware, then RDIMM probably the choice. Also RDIMM is significantly low cost than LRDIMM.

If you expand existing hardware instead of refresh hardware, then LRDIMM is the choice since it give you  same capacity but reserves few DIMM slots. Another reason is cost per memory operation of LRDIMM is lower than RDIMM.

I have a farm that mixed by LRDIMM and RDIMM ESXi 5.5 hosts. I really don't see any differencing from  performance perspective. If you are running mission critical application  on the farm, such as SAP, Oracle, or SQL. Then LRDIMM is always best choice.

References:

A memory primer for new BL460cGen8 blades with Intel Ivy Bridge Processors

Is LRDIMM the best memory option for an enterprise server?

LRDIMMs, RDIMMs, and Supermicro's Latest Twi

DDR4 RDIMM and LRDIMM Performance Comparison

Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install https://repo.ius.io/ius-release-el7.rpm yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm yum -y install https://packages.endpointdev.com/rhel/7/os/x86_64/endpoint-repo.x86_64.rpm yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "https://app.terraform.io/api/v2/organizations/ZHENGWU/organization-memberships?page%5Bsize%5D=100" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $Test.data.attributes.email