Re: Visual Basic to Oracle: how much thruput can I expect?

Keith,

    It depends on two things: (1) rowsize and (2) network throughput. Increasing the RAM on the client machines actually helps too (especially if you're CPU bound - believe it or not). What does the disk I/O on the client machines look like when doing SQL*Plus vs running your VB application? What does the disk I/O look like on the database server?

    In short, there are many tuning issues involved here. Your times are really bad unless you are running on a congested network with router problems or are trying to insert rows with large amounts of data (i.e., > 20k for example). 200 rows per second from the server is a good time for a machine with 2 CPU's and 1 GB RAM. I have a K460, a K570 and a K580. All with 4 GB or RAM and 4 CPU's (6 on the K580). Connection is through an ATM DS-3 SONET ring (88 MB/s), Visual Basic front-end through ODBC COM connectivity. Even at times with a network busy with traffic row inserts through SQL*Plus are in the 200-300 per second range, but all rows are < 20k each. Received on Sun Mar 14 1999 - 17:30:57 CET