UNSOLVED
T
Thierry101
2 Intern
•
326 Posts
0
1438
July 26th, 2012 21:00
AFTD performance
Hi folks
Just would like to check on performance tuning. Does the number applies to deduplication enabled hardware also like Data Domain or just normal disk configured as AFTD...there are two differing recommendations as below:-
Thanks
on 7.6.2 performance guide
AFTD device target and max sessions
This section describes for all supported operating systems, the optimal Advanced File
Type Device (AFTD) device target, and max sessions settings for the NetWorker
software.
NetWorker 7.6 Service Pack 1 and later
The defaults for AFTD target sessions and max device sessions are now set to the
optimal values for AFTD performance:
◆ Device target sessions is 1
◆ Device max sessions is 32 to avoid disk thrashing
If required, both Device target, and max session attributes can be modified to reflect
values appropriate for the environment.
On the DD integration guide
8. On the Configuration tab, set the number of concurrent save or clone streams
(sessions) the device may handle:
• Target sessions are the number of sessions that the NetWorker storage node
may send to this device before the storage node looks for another available
device. This should be set to a low value for best performance. The default
setting is 1 and it may not be set to a value greater than 60.
• Max sessions is set by default to a value of 10, which in most cases provides
best performance. It may not be set to a value greater than 60.
Thierry101
2 Intern
•
326 Posts
464
0
Posted August 12th, 2012 14:00
Hi Hrvoje
The two info were from 7.6.2 docos
From both quoted lines it is clear:
a) target session should be low and ideally 1
b) max session can't be more than 60 and they just disagree on what is the default value. Default value varies in some releases and perhaps same is truth for different builds of 7.6.2 - I plan to skip that one and jump to 7.6.3.x or even 7.6.4 in few weeks.
ble1
6 Operator
•
14354 Posts
•
56186 Points
464
0
Posted July 27th, 2012 02:00
Number of max sessions follows ddboost release and as you know NW8 and NW76SP2 use different releases. At the end of the day, this is more linked to DDOS and I suspect value given for NW8 applies to 5.2 code.