Do you have any of these in the DSM.OPT file? on a 100MB line I get around 10-15Megs/s transfer rate. Not sure if that is good, but ok for me. The resourceutilization 10 was a big help.
Joe Cascanette The Cumis Group Limited resourceutilization 10 Include.SystemObject ALL STANDARD txnbytelimit 25600 tcpwindowsize 1500 * or tcpwindowsize 0 - is use windows default tcpbuffsize 31 tcpnodelay yes -----Original Message----- From: Christoph Pilgram [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 13, 2001 10:49 AM To: [EMAIL PROTECTED] Subject: Performance on w2k Hi all, I have a a question concerning performance on a W2K-Client. On our W2K-fileserver (2 processors, 800000 files, w2k-compression on) we get a very poor performance with our backup (Vers. 4.2.0.0). With the performance monitor there seems not to be an problem with memory or CPU The bad time results from the scanning of the filesystem. In dsmsched.log you can see, that the system scans about 1000 to 1500 files per minute, what is compared to other systems very poor. I am not an expert in w2k so my question : is this normal for a w2k-system with that many files. Because there are sometimes a lot of rights belonging to one file, maybe there is a lot to compare with the filelist from the TSM-server ?? I saw in the XP-Client-Version an Problem fixed with IC31706, that reports of a performance problem in XP (what is the same TSM-Client), but this fix is not available for w2k. Has anybody an idea where the problem comes from and how it can be fixed ? Thanks a lot Chris
