For smaller queries it doesn't hit the disk much but we have a couple of tables that have ~100k records and when the app queries (which have joins) hit with minimal parameters bam!, HD lights up like a Christmas tree and everyone comes to a screeching halt.
I got some ideas from Alex that I am going to try, plus maybe have the JDBC driver allow dirty reads. I am trying to get funds to beef up the server to a dual proc w/ mucho ram and raid so maybe that will help a bit as well. Thanks for the info, at least I know I am not going crazy. -----Original Message----- From: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 11:39 AM To: Kevin Wilson; Sapdb General List (E-mail) Subject: RE: 1 Process handles 99.9% of load ... Hi Kevin, We have seem this too. I bet your hard drives are constantly in use. Your 99.9% of load seems to imply CPU, what about disk I/O? SAPDB kernel does not seem to like to "multitask" I/O. Even though a small query may only need to do 10 pages of I/O, a larger query doing thousands of pages of I/O will make the remaining SQL statements all queue. We have seen the same problem you describe when two different clients (web servers) are accessing a common SAPDB server over TCP/IP - so it isn't just an issue with drivers. Also note that 7.4 series has not improved things much. In fact, the most recent release of 7.4 seemed to increate our disk I/O by about 20% slowing our database down further. Stephen Gutknecht currently in Seattle, Washington USA -----Original Message----- From: Kevin Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 7:15 AM To: Sapdb General List (E-mail) Subject: 1 Process handles 99.9% of load ... but makes other requests wait even though there are 50 processes allocated to handle connection requests. [System] SAPDB v7.3.0.34 (w/ corresponding JDBC driver) SuSE v8.1 Java v1.4.1_01 Tomcat v4.1.18 [Background] I have two jsp webapps that access a single sapdb instance but each with a different user account that own their respective application database objects. ***One app uses SSL and the other does not.*** [Issues] One process seems to be handling 99.9% of all the service requests. This holds true even when other requests are waiting to be serviced while this one process is busy. A second problem is that it seems that read queries are locking down tables. I may be mistaken but we have one table that is huge and whenever an intensive query is ran it locks out other users wanting to access the table with a read query. Any advice on parameters to tweak, etc. would be appreciated. Thanks, Kevin "Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, 1759 _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
