Anybody consciously set this to something other than the default value of 50?
If you have raised it, why did you do so, and more importantly, did you see any negative impact on the *toaster*?
We're currently at 253 in one of our environments, and we're being asked to bump it to the maximum recommended value (1124).
I've read the NOW articles on the parameter, so no need to explain what it is or how it works. I'm just looking for experience, good or bad, for raising it to the much larger values.
This environment already has our Windows machines beating the crap out of a handful of 6070's, and I'm proceeding cautiously before giving each Windows client EVEN MORE connections to the toasters...
Until next time...
The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill@mathworks.com http://www.mathworks.com ---
low the deswizzling to complete. We are running 7.2.4, which doesn't have the apparent deswizzle re-start capabilities in later versions.
We stopped all regular snapshots, all snapmirrors, and all snapvaults to the volumes in question, and let the deswizzling run from Friday night through the weekend. By Tue morning, it wasn't finished. :(
So, the next weekend, we stopped all snapshot activity *and* deleted all but two snapshots on the affected volumes (we had 30-40 prior). That was barely enough...the deswizzle scans finished by 7 AM the following Tuesday.
These weren't extraordinary volumes...just user data (home directories) with volume sizes of about 500 GB with a couple million files.
So, we are back to normal operating load levels now. Yea!
(I think a knowledge base article on NOW is in order for this consequence of running volume snapmirrors. It took us by surprise, and it took the collective knowledge of this mailing list to nail down the answer.)
Until next time...
The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill@mathworks.com http://www.mathworks.com ---
I think we are also at 253. We have a lot of citrix servers....each with up to 200-250 citrix sessions on it at the same time. We did not see anything on the downside after making the change....we did it based on the output of cifs stats
HTH Jack
Todd C. Merrill wrote:
Anybody consciously set this to something other than the default value of 50?
If you have raised it, why did you do so, and more importantly, did you see any negative impact on the *toaster*?
We're currently at 253 in one of our environments, and we're being asked to bump it to the maximum recommended value (1124).
I've read the NOW articles on the parameter, so no need to explain what it is or how it works. I'm just looking for experience, good or bad, for raising it to the much larger values.
This environment already has our Windows machines beating the crap out of a handful of 6070's, and I'm proceeding cautiously before giving each Windows client EVEN MORE connections to the toasters...
Until next time...
The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill@mathworks.com http://www.mathworks.com
I believe the other option (NOW site has more detail) was 1153. So long as the settings match on both sides (NetApp and Windows), you should be in good shape with no negative effects.
There is a registry setting introduced in windows a few years back that allows for a single TCP\CIFS session per user session, rather than a TCP\single CIFS session shared by all users.
Glenn
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Jack Lyons Sent: Thursday, November 13, 2008 6:42 PM To: Todd C. Merrill Cc: toasters@mathworks.com Subject: Re: options cifs.max_mpx
I think we are also at 253. We have a lot of citrix servers....each with up to 200-250 citrix sessions on it at the same time. We did not see anything on the downside after making the change....we did it based on the output of cifs stats
HTH Jack
Todd C. Merrill wrote:
Anybody consciously set this to something other than the default value of 50?
If you have raised it, why did you do so, and more importantly, did
you
see any negative impact on the *toaster*?
We're currently at 253 in one of our environments, and we're being asked to bump it to the maximum recommended value (1124).
I've read the NOW articles on the parameter, so no need to explain
what
it is or how it works. I'm just looking for experience, good or bad, for raising it to the much larger values.
This environment already has our Windows machines beating the crap out of a handful of 6070's, and I'm proceeding cautiously before giving each Windows client EVEN MORE connections to the toasters...
Until next time...
The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill@mathworks.com
-
Glenn Walker -
Jack Lyons -
Todd C. Merrill