Why async I/O?
(OLTP) application, you have many connections (over 200 connections) and short transactions: get this row, update that row. These transactions are typically spread across different tables of the databases. The ASE can then perform each one of these asynchronously without having to wait for others to finish. Hence the importance of having async I/O fixed on our platform. Engines Sybase System 10 can have more than one engine (as stated above). Sybase has trace flags to pin the engines to a given CPU processor but we typically don’t do this. It appears that the master engine goes to processor 0 and subsequent subordinates to the next processor. Currently, Sybase does not scale linearly. That is, five engines do not make Sybase perform five times as fast however we do max out with four engines. After that performance starts to degrade. This is supposed to be fixed with Sybase System 11. Putting Everything Together As previously mentioned, an ASE is a collection of databases with connectio
