Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: high through put system

Re: high through put system

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Wed, 23 Aug 2006 09:12:28 +0200
Message-ID: <aovne2le5mioop331106lf33l55lb7ppmj@4ax.com>


On 22 Aug 2006 22:42:44 -0700, vissuyk_at_yahoo.com wrote:

>Hi All,
>
>We have a Servlet application that has to process 10K requests per
>second. In every request, we need to perform one lookup and one insert
>operation. The data size per select/insert is about 1K (makes up one
>row).
>
>We are using Oracle 10.2. We are no where near the needed through put.
>How can we scale this application?. Any suggestions are appreciated.
>Any proven patterns will be very much appreciated. We are going to have
>RAC too (soon), but this wont add to the tyhroughtput, I see it is a
>increasing the availability.
>
>ANy thoughts or ideas are appreciated.
>
>Thanks
>
>Vissu

You aren't using bind varianles, are you? Not using bind variables is the #1 method to make Oracle unscalable. Also, this doesn't look much like an interactive app, so why aren't you using the right tool for the right job (like Sql*loader and similar)?
If you have to use an interactive process, you should be performing BULK COLLECT and BULK INSERT, not 1 row at a time, and definitely NOT 1 commit PER RECORD.

Your post has 'badly engineered app' inscribed all over it.

--
Sybrand Bakker, Senior Oracle DBA
Received on Wed Aug 23 2006 - 02:12:28 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US