VMware

Chuck8773

Chuck8773's Profile

  • Name: Charles 
  • Email: (Private)
  • Member Since: May 4, 2007
  • Last Logged In: Nov 19, 2009 6:34 AM
  • Status Level: Expert Expert (880 points)
  • Location: Central Minnesota
  • Occupation: Infrastructure Analyst
  • Signature: Charles Killmer, VCP4 If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

Chuck8773's Latest Content

After looking for a good description of Active Memory and posting a question with no responses, I decided to just put it to the test. I wrote a small C++ app that would either write to or read from 500 MB of RAM. Here is what I learned.

My first run through the program wrote a random character to every index in the 500 MB array.

Next it wrote to random indexes.

Next it read from random indexes.

In between all runs, the program was stopped and memory reclaimed by ESX.

It was about five minutes before the active memory counter in the VIC started to taper off.

So the easy description, "Active memory is memory that is either written to or read from within the last five minutes".


Charles Killmer

0 Comments Permalink

I have been impressed with many features of ESX4 and was again today. We currently, in ESX 3.5 U4, have VM's connect to their iSCSI volume with a software iSCSI initiator within the VM for performance reasons. This way we can give the VM multiple NICs in the SAN network and have it use multiple Gbps links to the volume. When using a VMDK on an iSCSI volume, we are llimited to a single Gbps link. That extra Gbps link or two really makes a difference.

With ESX4 supporting MPIO, we can now justify removing the iSCSI software from the VM and move all the data to a VMDK with a performance improvement, as the host has more connections to the SAN than the VM did.


Problem: In our current environment, when we snapshot the VM, system state is all that is snapped. Reverting only affects the system. If we move to VMDKs, now the snapshot affects data as well. This would be bad to roll back to a snapshot for an Exchange server.


Solution: Put the data VMDK into persistent mode so snapshots do not affect it. Great!


Another problem: Independent disks cannot be migrated with the VM online as snapshots cannot be taken.


Today I tested this on ESX4. It works. I have a VM with two disks, one is independent. Storage vmotion moved both disks.


Again, very impressed.


Charles Killmer

0 Comments Permalink

Write your own drafts, invite selected collaborators, or leave it open for all to pitch in.

Chuck8773's Blogs

Chuck8773's Tags

Communities