Compaq ProLiant 1000 Configuration and Tuning of Sybase System 11 for Microsof - Page 12

Configuration and Tuning of Sybase System 11 for Microsoft Windows NT on Compaq Servers Page 9 For larger data transfers between the clients and the server, such as BCP loads and unloads, it may be beneficial to increase this packet size to a higher value (2048 bytes and higher). In our testing of an OLTP parts order entry system a TDS packet size of 4096 bytes provided the best throughput. In a DSS environment a TDS packet size of 16384 bytes provided the best throughput. Experimentation is necessary to determine the best packet size for your environment. Multiple Network Protocols Windows NT and Sybase SQL Server support multiple network protocols. From the Control Panel, Network, Bindings, select Server to list the protocol bindings that are used by this Server. Take note of the protocol bindings listed. The Server will accept whatever protocol the Workstation/Client logs in with if it is listed here. Remove or disable any unused protocols to reduce the amount of system memory used by the network handlers. Adjusting the protocol binding order of the Server, Network Bindings has no effect on the server performance. If the same physical hardware platform that is running Sybase SQL Server is also acting as a Workstation/Client running Sybase SQL Monitor and/or Sybase Server Manager check the Workstation Network Bindings. If more than one protocol binding is listed, highlight and promote the protocol that is being utilized by Sybase SQL Monitor and/or Sybase Server Manager to the top of the listing. This will reduce the chances for failed logins and network protocol timeouts on a heavily loaded system. Refer to the Microsoft Windows NT Server, System Guide for more detail on this subject. Performance Monitoring and Tuning A concise method exits for the altering and verifying the many tuning parameters that effect the performance of Sybase SQL Server release 11 for Windows NT. All configurable items in System 11 are stored external to the database in an ASCII format data file of the name, servername.cfg. This makes it possible to quickly fix any configuration errors with a text editor like Notepad without the hassles of previous version via the buildmaster utility. System Processor Utilization, Monitoring and Optimization This section provides information on parameters that you can set to influence performance from the system processor perspective and tools you have available to monitor the behavior of the system. Optimizing Windows NT & SQL Server Operations By default, all Sybase SQL Server threads fall into the variable priority class, priorities ranging from 1 to 15. Most threads in the system, including applications, fall into this class, and the Windows NT dispatcher can vary the priority of these threads to optimize system response time. Another priority class exists, called real-time priority class, with priorities ranging from 16 to 31, and is used by time-critical applications requiring immediate processor attention. Once a thread runs in the variable priority class, its priority cannot be dynamically raised to the real-time class, and vice versa. The Tasking option setting determines how Windows NT schedules base thread priorities. The default setting of Best Foreground Application Response Time schedules the initial foreground base thread priority at level 9 and the background base thread priority will be level 7. If you choose Foreground Application More Responsive than Background the initial foreground base thread priority is at level 8, background base thread priority remains at 7. If you choose the setting Foreground and Background Applications Equally Responsive the initial foreground and background base thread priority will be at level 7. © 1996 Compaq Computer Corporation, All Rights Reserved Doc No 143A/0596