search

NetAppDocs / flexpod

https://docs.netapp.com/us-en/flexpod/
0 stars 4 forks source link

Single volume not always best #9

Closed MrObvious closed 1 year ago

MrObvious commented 3 years ago

Page: Best practices

This may require consultation with O'Mahoney or Jeff Steiner, but single LUN/Volume setups on anything more than like 4-6 CPU cores really drag with performance. Multiple volumes/LUNs are better to avoid single affinity/scsit_lu thread bottlenecks.

DrKeno commented 2 years ago

Is this still true with the single LUN performance improvements in ONTAP 9.9.1?

MrObvious commented 2 years ago

Perhaps not, but we still hit single affinity bottlenecks. Flexgroups are the obvious answer to that.

netapp-jyhshing commented 2 years ago

Asked Bobby to help take a look.

ntap-bmegan commented 1 year ago

@netapp-jyhshing - Please update status or close if work is complete.

ntap-bmegan commented 1 year ago

@netapp-jyhshing - What is the status of this issue?

netapp-jyhshing commented 1 year ago

Let me check with Bobby. Thanks.

bobbyoommen commented 1 year ago

Thanks for pointing this out. @MrObvious I am fixing it. "Place database files in a single FlexVol; don’t spread them across FlexVols". Not sure how it fell thru the crack.

Single LUN performance made significant improvement over past ONTAP releases, and could cover most of the DB use-cases in SMB, but I have seen customers running in challenges when they look for larger throughput [backups].

thank you @ntap-bmegan and @netapp-jyhshing

bobbyoommen commented 1 year ago

@MrObvious - The change is implemented.

ntap-bmegan commented 1 year ago

Can we close the issue, or is additional work required?

bobbyoommen commented 1 year ago

I am good closing. was waiting for @MrObvious