|
>
"Properties that affect Web proxy use" in EAServer Security Administration and Programming Guide
Section 6: Protocols
Category
Performance Considerations
More Information
SSL
SSL Session Share, and SSL Session Linger
SSL reuses the previously negotiated security session parameters in a number of short-lived connections, which results in a relatively large performance gain over setting up completely new security sessions for each connection. When a security session is reused, clients avoid a CPU-intensive encryption of the premaster-secret using the server's public key. Similarly, servers avoid a CPU-intensive decryption of the premaster-secret using its private key. By configuring these parameters, you can control SSL caching on the server side.
"Defining security profiles" in EAServer Security Administration and Programming Guide
IIOP
HTTP-tunnelled IIOP connections
The com.sybase.jaguar.server.http.force.close property specifies whether HTTP-tunnelled IIOP connections should be closed after sending each IIOP response. When debugging proxy configurations, you can set this property to true if it helps your debugging efforts. This setting degrades server performance, so it should only for debugging purposes.
"Repository Properties Reference" in EAServer System Administration Guide
Section 7: Web Server Redirector Plug-Ins
Category
Performance Considerations
More Information
Connection timeout
com.sybase.jaguar.listener.http.conn.keepalive
This is an optional property that specifies the length of time, in seconds, to keep a connection alive before it is closed by EAServer. The default value is 120 seconds (2 minutes) and can be modified, if necessary, to improve performance.
"Configuring EAServer to accept Web server requests" in EAServer System Administration Guide
Maximum requests
com.sybase.jaguar.listener.http.conn.maxrequests
This optional property determines the number of requests processed before EAServer closes the connection. The default value is 100 and can be modified, if necessary, to improve performance.
"Configuring EAServer to accept Web server requests" in EAServer System Administration Guide
Tracing
Set the log level property to Inform or Error instead of Verbose.
"Editing the redirector configuration file" in EAServer System Administration Guide
Section 8: Database Access
Good database and query design is essential for database performance in general. Additionally, these suggestions are applicable to working with databases in EAServer.
Category
Performance Considerations
More Information
Physical Database Connections
Physical database connects are very expensive. You can reduce the cost using EAServer connection caches. A connection cache maintains a pool of connections to a database\ server, increasing performance by allowing connection sharing and reuse. Since more clients can be serviced using fewer third-tier connections, CPU time and memory are not consumed by opening more connections than necessary.
"Using Connection Management" in EAServer Programmer's Guide
Connection Cache Tuning
You can set the pool size using the Number of Connections in Cache property. After a connection is released, it is returned to the pool. The default value is 10. You can increase this number if performance suffers due to an insufficient number of available connections. To tune the number of connections, use runtime monitoring to ensure that there is not a large number of Forced Connections.
"Connection cache properties" in EAServer System Administration Guide
Connection Cache Sanity Checking
Disable connection sanity check. When the option is enabled, EAServer verifies that the connection is open and accepts commands before making it available for reuse. Disabling the option increases performance, but may complicate debugging. For example, components may release a connection that is not ready for use by another component, such as when there is unretrieved results on the connection.
"Connection cache properties" in EAServer System Administration Guide
Connection Management in C, C++, and ActiveX components
ActiveX, C, and C++components can call the Connection Manager routines to take advantage of connection caching. These routines manage caches of ODBC, Client-Library, or Oracle Call Interface (OCI) connections. When there are many configured caches, a component can achieve better performance by passing the cache handle explicitly in JagCmGetConnection to eliminate repeated internal table searches.
"Using Connection Manager routines in C, C++, and ActiveX components" in EAServer Programmer's Guide
XA Resources
Be aware that XA performance diminishes when connections span across methods.
"Configuring XA resources" in EAServer System Administration Guide
JDBC Drivers
JDBC driver properties can also provide good performance boots depending on what you enable/disable.
To help you choose a driver type, read the JavaWorld article " JDBC drivers in the wild" to learn the differences between JDBC driver types, and how to benchmark them.
Documentation for the JDBC driver you are using
jConnect
The jConnect documentation includes a chapter devoted to the ways to fine-tune and improve performance when working with jConnect.
Performance and Tuning chapter in Programmer's Reference jConnect for JDBC
ODBC
ODBC 3.0 drivers generally perform better than older versions.
ASA
ASA can run on multiple processors, has an advanced query optimizer, and provides performance monitoring and tuning tools.
ASE
- SYC Interface
Ensure that ASE connection caches are defined to use the SYJ interface, since the SYC interface does not utilize the cache at all.
- UNIX File Descriptors
On UNIX platforms, ensure the operating system allows enough file descriptors to handle the number of connections you wish to allow.
"Configuring Adaptive Server Enterprise connections" in EAServer System Administration Guide
Database Driver Tracing
Ensure tracing features for the database driver are not enabled, as this can severely degrade performance
Section 9: Web Services Toolkit
Category
Performance Considerations
More Information
Trace and Debug
When generating WSDL or SOAP templates, do not include the -d or -t flags for debug or trace output
Web Services Toolkit User Guide
Section 10: System-Level Tuning and Sizing
Category
Performance Considerations
More Information
Sizing
See TechWave 2001 presentation http://techwave.sybase.com/2001_presentations/ID333.zip
Multiprocessors
Some operating systems fully utilize multiple CPUs, while others do not. Depending on the OS you are using, you may need to bind EAServer to each CPU in order to take advantage of the multiple processors.
Binding a Process to a CPU on Windows NT or Sun Solaris (written for PB but applies generically)
Section 11: Runtime Monitoring and Stress Testing
Category
Performance Considerations
More Information
EAServer Monitoring Tools
Use the File Viewer, Runtime Monitor, and the OTS Transaction Monitor to track EAServer's performance and statistics.
"Runtime Monitoring," in EAServer System Administration Guide
上一页 [1] [2] [3] [4] [5] [6] [7] [8] 下一页
[SyBase]用Sybase EAServer建立电子影院售票系统 [SyBase]Index & Performance
[SyBase]Optimizing SQL Anywhere performance over a WAN [ORACLE]ORACLE PERFORMANCE SQL TUNING
[ORACLE]Oracle Tuning (Oracle 性能调整)的一些总结
| 
注：本站部分文章源于互联网，版权归原作者所有！如有侵权，请原作者与本站联系，本站将立即删除！ 本站文章除特别注明外均可转载，但需注明出处！ [MinTao学以致用网] 
