2 aggrs give you more available WAFL affinities (cpu threads for parallel write metadata operations) which will help performance - especially with flexgroup volumes. But you do lose disks to parity. You’ll want to weigh capacity vs. potential performance.

Get Outlook for iOS

From: Toasters <toasters-bounces@teaparty.net> on behalf of Tony Bar <tbar@berkcom.com>
Sent: Monday, June 29, 2020 7:52:49 PM
To: NGC-michael.bergman-ericsson.com <michael.bergman@ericsson.com>
Cc: Toasters <toasters@teaparty.net>
Subject: Re: single or multiple aggregates?
 
NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.



9.7 P4/P5 is definitely the place to be right now — if your system can run it (check https://hwu.netapp.com to see)   There are a couple ugly bugs in the GA 9.7 and P1-P3 but P4/P5 ironed those out and it’s very stable, and there are a lot of performance improvements (esp. if you run on an AFF). The new low-end AFF (c190) is a really great deal price-wise too for a small deployment.   

Anthony Bar

tbar@berkcom.com

www.berkcom.com



On Jun 29, 2020, at 3:38 PM, Michael Bergman <michael.bergman@ericsson.com> wrote:

On 2020-06-29 21:15, John Stoffel wrote:
How many volumes are you running in each SVM?  But basically in my
experience it's not too big a deal to have different SVMs sharing
aggregates.  This bigger deal is having SATA vs SAS on the same head,
at least with older versions.  I'm running 9.3 these days and not
seeing problems.

Indeed, there's no problem having many vservers share Aggregates. That was
never an issue, really. Certainly not ONTAP 9 and up.  And the problem with
CP processing (WAFL Consistency Point) you mention was solved long ago. I.e.
mixing 10K rpm and 7.2K rpm Aggregates in the same controller.
Really: 9.7 is a good place to be all in all. It has many carefully thought
out performance tunings in WAFL and other places which earlier versions do
not have

/M