abeNd.org - Tuning TSA for better performance ?

User Functions
Username: Password: Don't have an account yet? Sign up as a New User Lost your password?

What's New
STORIES No new stories COMMENTS last 2 days No new comments TRACKBACKS last 2 days GroupWise 2012 no... LINKS last 2 weeks No recent new links

Who's Online
Guest Users: 8

Live Novell Chat
Live Novell Chat

Topics
Home Poll posts (1/0) Way Off Topic! (1/0) Contracting (2/0) FAQ (1/0) NetWare (51/0) Certification (31/0) NDS/eDir (19/0) Administration (78/0) GroupWise (143/0) Linux/Open Source (309/0) Resources (21/0) General News (904/0) Security (291/0)

Poll
How do you think the Attachmate deal will turn out for "Novell" Well, the marketing can't be any WORSE Better, the product/support commitment is there Worse, MS will end up with what is left of Novell’s marketshare & still end up with the patents, leaving the customer as the loser Results 86 votes \| 0 comments

Poll
Does your company still use Blackberry phones? Yes, with BES Yes, without BES No, we never used Blackberries No, we just stopped using them No, we stopped using them 6 months ago No, we stopped using them 1+ year ago Results 55 votes \| 0 comments

Novell Advisor
There was a problem reading this feed (see error.log for details).

Tuning TSA for better performance ?

Author:	Zero
Dated:	Wednesday, April 13 2005 @ 05:59 PM CDT
Viewed:	3,838 times

In dealing with a lot of migration wizard problems, mostly due to the amount of time it takes to backup/restore trustees, I decided to inquire about TSA performance tweaks and recieved the following response. I havent tried any of these yet, but maybe they'll be beneficial...

Here's some comments from the SMS engineers:
Looks like he is talking about the ReadBufferSize.

Tuning TSA depends on the mean file size of the system being migrated. If the source system has larger files(1Mb files), then setting ReadBufferSize to 128k will help perform better.

But the default setting is good enough for normal servers. If the source server has multiple Processors then increasing the ReadThreadsPerJob will help TSA perform better. By default the value is 4, if the source server has 2 or more processors then increasing this to 8 or 12 will help in read performance.

Also setting the "CacheMemoryThreshold" switch to 5 to 10% (if not already set) will ensure optimal usage of memory. This switch denotes the percentage of free server memory to be used for caching the files (at an average 40-50MB is good enough). If the System has 512MB RAM, setting it to 15% will be good. More the RAM less the value.

These are the available Tuning parameters in SMS.

If NSS filesystem is migrated, then setting the CacheBalance in NSS tuning parameters to 50 will help performance of large files. Also setting the ReadAheadBlks for the particular NSS volume would help if the files are large enough (100k or more).

BTW, all these TSA switches are only present in TSAFS. It can be configured using iManager or from the console. Use TSAFS /help for more information on setting.

More information on configuring TSAFS can be found in the following link http://www.novell.com/documentation/oes/index.html?page=/documentation/oes/smsadmin/data/am8mern.html

What's Related
http://www.novell.com/... More by Zero More from Administration

Story Options
Mail Story to a Friend Printable Story Format

Trackback

Trackback URL for this entry: http://www.abend.org/trackback.php/20050413175929118

No trackback comments for this entry.

Tuning TSA for better performance ? | 1 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Tuning TSA for better performance ?

Authored by: ph0bia on Wednesday, April 13 2005 @ 07:16 PM CDT

Awesome - this could be really handy for speedier migrations and backups....

Welcome to abeNd.org - Novell News for IT Professionals Saturday, February 04 2012 @ 04:15 AM CST

Trackback