- VMware Technology Network
- :
- Cloud & SDDC
- :
- vSAN
- :
- VMware vSAN Discussions
- :
- Re: VSAN 6.7 U3 performance data in relation to wi...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VSAN 6.7 U3 performance data in relation to win10 WSL2 build.
I have a question, how do I see performance data of vsan, specifically cache data and hit rate
I have put new Windows10 WSL2 build ( which is preview ), in vsan and performance is amazing. About 400Meg in both read and write.
I used parkdale to measure.
how do I know , that my windows 10 is properly using cache SAN disk. May be I want to tune that too - like increasing the read cache and decreasing the write cache. The command line stuffs are still not there , seems like to tune.
I have below configuration
[root@myesx2:~] df
Filesystem Bytes Used Available Use% Mounted on
VMFS-5 367756574720 97726234624 270030340096 27% /vmfs/volumes/datastore1
VMFS-6 375541202944 298055630848 77485572096 79% /vmfs/volumes/datastore2
VMFS-6 429228294144 356474945536 72753348608 83% /vmfs/volumes/Backup
VMFS-6 1073473388544 419461857280 654011531264 39% /vmfs/volumes/BackupOnlySSD
vfat 261853184 154546176 107307008 59% /vmfs/volumes/e41e6274-1dadf5e9-fe37-c54656a3fe10
vfat 4293591040 98238464 4195352576 2% /vmfs/volumes/5aecb7ec-15ffa907-1e74-000c294f53fa
vfat 299712512 182247424 117465088 61% /vmfs/volumes/55c36ca4-10bf7a0d-1a46-000c29d07b5e
vfat 261853184 155942912 105910272 60% /vmfs/volumes/5cc7917f-0c02a7b6-4769-19908b34928c
vsan 966359252992 89409894481 876949358511 9% /vmfs/volumes/vsanDatastore
[root@myesx2:~]
[root@myesx2:~] esxcli vsan cluster new [J
[root@myesx2:~] esxcli vsan clusterget [J
[root@myesx2:~] esxcli vsan cluster get [J
Cluster Information
Enabled: true
Current Local Time: 2019-08-29T18:19:29Z
Local Node UUID: 55c36bdc-60c1-02d2-5d5d-000c29d07b5e
Local Node Type: NORMAL
Local Node State: MASTER
Local Node Health State: HEALTHY
Sub-Cluster Master UUID: 55c36bdc-60c1-02d2-5d5d-000c29d07b5e
Sub-Cluster Backup UUID:
Sub-Cluster UUID: 52e311a7-aca8-66d1-b445-aeee1cf29efb
Sub-Cluster Membership Entry Revision: 0
Sub-Cluster Member Count: 1
Sub-Cluster Member UUIDs: 55c36bdc-60c1-02d2-5d5d-000c29d07b5e
Sub-Cluster Member HostNames: myesx2.localdomain
Sub-Cluster Membership UUID: fc16685d-67bd-4aa0-b8f3-000c293d1e68
Unicast Mode Enabled: true
Maintenance Mode State: OFF
Config Generation: None 0 0.0
[root@myesx2:~]
[root@myesx2:~] esxcli vsan cluster get [J [J [J [J [J [J [J [J [J [J [J [Jstorage list
t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001
Device: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001
Display Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001
Is SSD: true
VSAN UUID: 520602de-711a-9cb1-768e-e2c676411aa8
VSAN Disk Group UUID: 528d26a2-1a58-3b42-47d7-ed46c46d6158
VSAN Disk Group Name: mpx.vmhba1:C0:T3:L0
Used by this host: true
In CMMDS: true
On-disk format version: 10
Deduplication: false
Compression: false
Checksum: 4593535388370434937
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Thu Aug 29 18:16:19 2019
mpx.vmhba1:C0:T3:L0
Device: mpx.vmhba1:C0:T3:L0
Display Name: mpx.vmhba1:C0:T3:L0
Is SSD: true
VSAN UUID: 528d26a2-1a58-3b42-47d7-ed46c46d6158
VSAN Disk Group UUID: 528d26a2-1a58-3b42-47d7-ed46c46d6158
VSAN Disk Group Name: mpx.vmhba1:C0:T3:L0
Used by this host: true
In CMMDS: true
On-disk format version: 10
Deduplication: false
Compression: false
Checksum: 13283692042793370515
Checksum OK: true
Is Capacity Tier: false
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Thu Aug 29 18:16:19 2019
[root@myesx2:~] =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2019.08.29 14:38:47 =~=~=~=~=~=~=~=~=~=~=~=
and what is healthy 9 means ?
[root@myesx2:~] esxcli vsan debug object health summary get
Health Status Number Of Objects
--------------------------------------------------------- -----------------
reduced-availability-with-no-rebuild 0
reducedavailabilitywithpausedrebuild 0
reducedavailabilitywithpolicypending 0
nonavailabilityrelatedincompliancewithpausedrebuild 0
reduced-availability-with-active-rebuild 0
inaccessible 0
nonavailability-related-incompliance 0
data-move 0
healthy 9
reducedavailabilitywithpolicypendingfailed 0
reduced-availability-with-no-rebuild-delay-timer 0
nonavailabilityrelatedincompliancewithpolicypendingfailed 0
nonavailability-related-reconfig 0
nonavailabilityrelatedincompliancewithpolicypending 0
[root@myesx2:~]
[root@myesx2:~] esxcli vsan debug object list
Object UUID: f849685d-6f70-cb04-6b7c-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 6.00 GB
Used: 6.00 GB
Policy:
proportionalCapacity: 100
hostFailuresToTolerate: 0
forceProvisioning: 1
stripeWidth: 1
CSN: 1
Configuration:
Component: f849685d-2983-2807-8976-000c293d1e68
Component State: ACTIVE, Address Space(B): 6442450944 (6.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 6580862976 (6.13GB), Physical Capacity Used(B): 6446645248 (6.00GB), Host Name: myesx2.localdomain
Type: vmem
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/7b33685d-c4e3-5673-d687-000c293d1e68/windows101950-19f61d1f.vmem (Exists)
Group UUID: 7b33685d-c4e3-5673-d687-000c293d1e68
Directory Name: N/A
Object UUID: 3b19685d-6bbf-fd0c-6618-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 0.09 GB
Used: 0.10 GB
Policy:
proportionalCapacity: [0, 100]
hostFailuresToTolerate: 0
forceProvisioning: 1
stripeWidth: 1
CSN: 3
Configuration:
Component: 3b19685d-72eb-bc0d-dae3-000c293d1e68
Component State: ACTIVE, Address Space(B): 98566144 (0.09GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 109051904 (0.10GB), Physical Capacity Used(B): 104857600 (0.10GB), Host Name: myesx2.localdomain
Type: vmswap
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/3a19685d-60a2-b835-a466-000c293d1e68/vmx-Windows10-4224861040-1.vswp (Exists)
Group UUID: 3a19685d-60a2-b835-a466-000c293d1e68
Directory Name: N/A
Object UUID: 573d685d-e439-1a16-bae4-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 6.00 GB
Used: 6.00 GB
Policy:
proportionalCapacity: 100
hostFailuresToTolerate: 0
forceProvisioning: 1
stripeWidth: 1
CSN: 1
Configuration:
Component: 573d685d-f5ed-0b18-729a-000c293d1e68
Component State: ACTIVE, Address Space(B): 6442450944 (6.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 6580862976 (6.13GB), Physical Capacity Used(B): 6446645248 (6.00GB), Host Name: myesx2.localdomain
Type: vmem
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/7b33685d-c4e3-5673-d687-000c293d1e68/windows101950-Snapshot1.vmem (Exists)
Group UUID: 7b33685d-c4e3-5673-d687-000c293d1e68
Directory Name: N/A
Object UUID: 7c33685d-c5d6-151f-3cb8-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 50.00 GB
Used: 11.40 GB
Policy:
forceProvisioning: 1
hostFailuresToTolerate: 0
proportionalCapacity: 100
CSN: 2
Configuration:
Component: 7c33685d-0ac8-f31f-45ac-000c293d1e68
Component State: ACTIVE, Address Space(B): 53687091200 (50.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 54777610240 (51.02GB), Physical Capacity Used(B): 12238979072 (11.40GB), Host Name: myesx2.localdomain
Type: vdisk
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/7b33685d-c4e3-5673-d687-000c293d1e68/windows101950.vmdk (Exists)
Group UUID: 7b33685d-c4e3-5673-d687-000c293d1e68
Directory Name: N/A
Object UUID: 6631685d-cb34-f826-963d-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 6.00 GB
Used: 6.00 GB
Policy:
proportionalCapacity: 100
hostFailuresToTolerate: 0
forceProvisioning: 1
stripeWidth: 1
CSN: 1
Configuration:
Component: 6631685d-202c-0829-eb5f-000c293d1e68
Component State: ACTIVE, Address Space(B): 6442450944 (6.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 6580862976 (6.13GB), Physical Capacity Used(B): 6446645248 (6.00GB), Host Name: myesx2.localdomain
Type: vmem
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/3a19685d-60a2-b835-a466-000c293d1e68/Windows10-bdf99cad.vmem (Exists)
Group UUID: 3a19685d-60a2-b835-a466-000c293d1e68
Directory Name: N/A
Object UUID: 3a19685d-60a2-b835-a466-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 255.00 GB
Used: 70.36 GB
Policy:
proportionalCapacity: [0, 100]
hostFailuresToTolerate: 0
forceProvisioning: 1
stripeWidth: 1
CSN: 3
Configuration:
Component: 3a19685d-fd26-c336-d5b4-000c293d1e68
Component State: ACTIVE, Address Space(B): 273804165120 (255.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 76311166976 (71.07GB), Physical Capacity Used(B): 75551997952 (70.36GB), Host Name: myesx2.localdomain
Type: vmnamespace
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/Windows10 (Exists)
Group UUID: 3a19685d-60a2-b835-a466-000c293d1e68
Directory Name: Windows10
Object UUID: 583d685d-0fe0-b05f-ef63-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 50.00 GB
Used: 9.63 GB
Policy:
forceProvisioning: 1
hostFailuresToTolerate: 0
proportionalCapacity: [0, 100]
CSN: 2
Configuration:
Component: 583d685d-3d6d-dc61-6904-000c293d1e68
Component State: ACTIVE, Address Space(B): 53687091200 (50.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 10443816960 (9.73GB), Physical Capacity Used(B): 10338959360 (9.63GB), Host Name: myesx2.localdomain
Type: vdisk
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/7b33685d-c4e3-5673-d687-000c293d1e68/windows101950-000001.vmdk (Exists)
Group UUID: 7b33685d-c4e3-5673-d687-000c293d1e68
Directory Name: N/A
Object UUID: 7b33685d-c4e3-5673-d687-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 255.00 GB
Used: 0.37 GB
Policy:
proportionalCapacity: [0, 100]
hostFailuresToTolerate: 0
forceProvisioning: 1
stripeWidth: 1
CSN: 1
Configuration:
Component: 7b33685d-198e-3674-0034-000c293d1e68
Component State: ACTIVE, Address Space(B): 273804165120 (255.00GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 398458880 (0.37GB), Physical Capacity Used(B): 394264576 (0.37GB), Host Name: myesx2.localdomain
Type: vmnamespace
Path: /vmfs/volumes/vsan:52e311a7aca866d1-b445aeee1cf29efb/windows101950 (Exists)
Group UUID: 7b33685d-c4e3-5673-d687-000c293d1e68
Directory Name: windows101950
Object UUID: 572b685d-0020-73a5-247a-000c293d1e68
Version: 10
Health: healthy
Owner: myesx2.localdomain
Size: 70.55 GB
Used: 5.31 GB
Policy:
forceProvisioning: 1
hostFailuresToTolerate: 0
proportionalCapacity: [0, 100]
CSN: 1
Configuration:
Component: 572b685d-2470-daa6-92d8-000c293d1e68
Component State: ACTIVE, Address Space(B): 75750178816 (70.55GB), Disk UUID: 520602de-711a-9cb1-768e-e2c676411aa8, Disk Name: t10.NVMe____VMware_Virtual_NVMe_Disk________________VMWare_NVME2D0000____00000001:2
Votes: 1, Capacity Used(B): 5758779392 (5.36GB), Physical Capacity Used(B): 5700059136 (5.31GB), Host Name: myesx2.localdomain
Type: vdisk
Path: ./Windows10.vmdk.REDO_Id7o8v (Missing)
Group UUID: 3a19685d-60a2-b835-a466-000c293d1e68
Directory Name: N/A
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
You cannot tune the amount of write or read cache in vSAN. In an all-flash cluster, 100% of the cache is used for the writes. In a hybrid environment, 70% of the cache is used for reads, and 30% of the available cache is used for writes. It is configured this way for best performance by design.
In regards to your question regarding the command and output below. This command shows the Health Status of all the objects in your environment. You want all the objects to be listed under healthy. For more information on vSAN objects please see vSAN Terms and Definitions.
[root@myesx2:~] esxcli vsan debug object health summary get
Health Status Number Of Objects
--------------------------------------------------------- -----------------
reduced-availability-with-no-rebuild 0
reducedavailabilitywithpausedrebuild 0
reducedavailabilitywithpolicypending 0
nonavailabilityrelatedincompliancewithpausedrebuild 0
reduced-availability-with-active-rebuild 0
inaccessible 0
nonavailability-related-incompliance 0
data-move 0
healthy 9
reducedavailabilitywithpolicypendingfailed 0
reduced-availability-with-no-rebuild-delay-timer 0
nonavailabilityrelatedincompliancewithpolicypendingfailed 0
nonavailability-related-reconfig 0
nonavailabilityrelatedincompliancewithpolicypending 0