Re: How to improve performance using Oracle Spatial

   1. Find out where the code is spending its time. Best way I know to do
   that is extended SQL trace. (Actually, I believe it's the only way.) The
   trace data has an excellent chance of helping you even if the performance
   problem is caused by a non-database tier.
   2. Study the trace data to determine whether the time being spent is
   being spent legitimately, or wastefully.
   3. When you find waste, get rid of it. If you find no waste, celebrate
   that you have an efficient application. If it's efficient but still too
   slow, then it's time for a hardware upgrade.


Cary Millsap
http://method-r.com
http://carymillsap.blogspot.com


On Wed, Dec 31, 2008 at 1:12 PM, Jared Still <jkstill@xxxxxxxxx> wrote:

>
>
> On Wed, Dec 31, 2008 at 8:45 AM, Eriovaldo Andrietta <
> ecandrietta@xxxxxxxxx> wrote:
>
>> I need increase performance in my aplication.
>> It is using Oracle Spatial.
>> Could someone help me ?
>> All basic resources were applied.
>>
>> I am talking about a big database with 100.000 lines with geometry
>> datatype.
>> Using sdo_relate, sdo_join and others.
>> I think that database parameters must be reviews, Which ones ? PGA, SGA
>> Is there any in special ?
>>
>
>
> Wow, that's a pretty tall order.
>
> If performance is a problem, you will first need to determine exactly which
> part
> of the application is performing too poorly.
>
> The application users can tell you what parts are slow.
>
> They can also prioritize for you so that you work on the most important
> parts first.
>
> Then you need to determine where the bottlenecks are.
>
> From your email it seems that the assumption is that that database is at
> fault.
>
> That may or may not be the case.
>
> If transaction is taking 10 seconds, and it should take less than 1 second,
> you
> have to find out where the time is being spent.
>
> Then you need to pick the section(s) of the transaction that consume the
> most
> time, and determine what can be done to make them perform better.
>
> It's probably not a good idea to start tweaking database parameters in
> hopes
> that one may fix the problem.
>
> There are no silver bullets.
>
> That should give you a place to start.
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>
>
>

Other related posts: