On a related note to this, the promise of multi-threading and pulling more processes out of the kahuna domain was very much delivered in 8.1.1.  Prior to the upgrade we’d see 4 of 12 cores in the high 80’s and 90’s while 4-6 were literally at 0% and the rest were 10% or so.

After the upgrade it’s nearly  even across the board, a 5-6% spread among 12 cores, with the highest generally not going above 65%.

It’s been pretty good so far with one issue; if you have a traditional volume for root make sure to disable the cache re-warming feature that was added in 8.1.1.  If you don’t the entire cluster will panic after a few hours.  Once disabled (ahead of time hopefully) it’s not an issue.  Word on the street is it became a big enough issue with enough people that it will be fixed in 8.1.1p1.

But otherwise, a very nice release so far.

Jeff Kennedy

Qualcomm, Incorporated

QCT Engineering Compute

858-651-6592

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Randy Rue
Sent: Tuesday, September 18, 2012 1:28 PM
To: toasters@teaparty.net
Subject: RE: limit concurrent de-dupe processes?

found it>

sis.max_vfiler_active_ops

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Randy Rue
Sent: Tuesday, September 18, 2012 11:00 AM
To: toasters@teaparty.net
Subject: limit concurrent de-dupe processes?

Hello All,

I'm searching through previous stuff looking for this but hoping someone will know it offhand.

We're struggling with a v3170 running 7.3.5 that has a number of volumes being deduped automatically when their changed blocks hit 20%. You may know that the SIS process is a good example of a process that relies heavily on the Kahuna namespace and tends to hit one CPU hard while everything else stumbles.

Do I remember correctly that there's an option somewhere that limits the maximum number of concurrent SIS processes? Or do I need to script something weird.

Randy