A question then: What is your disk configuration? Are you separating logs and data dev spaces, for example? Are your drives and controllers fast enough? There is a lot written about Solaris disk io performance, so the problem might be closer to the OS than the DB if you are using file devspaces. What does iostat have to say?
Also, did you try raw dev spaces rather than file dev spaces? On Mon, 2002-10-07 at 16:14, XT Wang wrote: > > Here is the environment for my test > 1. I did test over both network and localhost. The result is the same. > 2. I also did 4 machine test, which machine run 4 instance. > 3. The test is basicly a simple insertion. Did the insertion through statement and >perpare statement. The data is no more than 65 bytes insert into a single table. So >there may have some table lock issue. > 4. I set the MAXCPU to 4. > Here is what I find out after spend days on it. > > the bottleneck is not CPU power. It is the disck IO. Windows NT always use buffered >IO on the io system. Use can use the PerfMon to watch the disk queue length jump when >the requests come in. UNIX has two kind of IO. The character device will physical >write data to disk. I test the Sybase Database two. Sybase, which is the base of M$ >SQL has about the same performance on my Sun box as the M$ SQL on PC Server. But >Sybase can change the configuration to use buffered IO, which 2 times faster than M$ >SQL. > > So my question is whether SAP DB can do the same or not. If it can, how do I >configure it. Although the data might not save when it is in the memory if the server >crash, but performance is much better. > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
