Re: sun sparc oracle solaris--- && troubles

I'll be (without even tuning the sql) that you don't have enough memory and your sga is being swapped out! You probably have 64 MB or maybe even 128 and your SGA is to big.

While i normally agree that a methodical troubleshooting plan should be followed, sometimes a bit of old-fashioned common sense or intuition will help.

There are no hard-and-fast rules.

Rod

In article <92uns2$o9q$1_at_news.sinet.slb.com>,   "Adam Soudure" <asoudure_at_slb.com> wrote:
> Yes, but simply upgrading the hardware is an expensive and short term
> solution.
> The best way to get better performance from your database is to tune
 it, and
> in this
> order: SQL Code --> RDBMS --> O/S --> Hardware.
>
> It is possbile that the original poster had a bit of SQL code that was
> inefficiently
> written, and required a bit of tweaking. I have personally seen this
 kind of
> tuning
> turn six hour reports into 35 second ones!
>
> I would look at the code first and run it through the explain plan. If
 it
> looks OK, then
> some tuning of the DB might be in order (ie SGA size, indexes on
 certain
> tables,
> layout of data files on the host etc etc). Only after those two steps
 would
> I entertain
> thoughts of new hardware.
>
> As for your assertion that Sun machines can't approach the speed of
 PC's, I
> say
> bollocks to that! The Sun machines in our data centre have it all over
 PC's
> in terms
> of workload capacity, speed, reliability and scalability. One of the
 E450's
> we have
> has about seven instances running at once, and more than adequately
 handles
> the
> workload.
>
> The other comment you make about programmer/vendor not being bothered
 with
> tuning
> code, fire the vendor!! If writing good PL/SQL or SQL code isn't part
 of
> their ethos, then
> you will find more problems than performance down the track. I can
 speak
> from personal
> experience on this one. I have had to look after an application that
 was
> badly written, and
> not only did it perform badly, it was full of bugs! It all came down
 to
> shoddy code....
>
> Cheers
>
> Adam
>
> <mend_at_my-deja.com> wrote in message

 news:92lgh3$qdr$1_at_nnrp1.deja.com...
> > That is too much hassle to do. The best way is use high speed
 hardware
> > to fix this problem. We have similiar performance problem. ON SUn
> > 1000E a sql statement run 10 minutes , same sql statement on dell
 2450 (
> > 1Ghz) only take 30 seconds. SUN computer CPU speed can not compare
 with
> > PC now. In theory, explain will help you the debug sql performance.
> > The problem is programmer or verdor don't want spent time on it.
> >
> >
> > In article <3A4CEB9B.CB8FBC39_at_usgs.gov>,
> > Troy Meyerink <meyerink_at_usgs.gov> wrote:
> > > If you want to see how Oracle is running the SQL, use the explain
 plan
> > > tool.
> > > Unless you write a lot of SQL, I wouldn't assume anything with the
 Oracle
> > > SQL parser. Also if you want help on tuning a system, you might
 want
 to
> > > provide more information about the system.
> > >
> > > Troy Meyerink
> > > Oracle DBA
> > > Raytheon
> > > USGS \ EROS Data Center
> > >
> > > siad_at_my-deja.com wrote:
> > >
> > > > hi all...
> > > > we have a sun station with solaris and oracle on it.......and
 its
> > > > incredible slow!!!
> > > > some statements take about 1 min (on my notebook few
> > > > secs)....especially a OR-clause in a statement with a 4table
 join
 gets
> > > > incredible slow....but if i devide the statement into 2
> > > > statements....the 2 are very fast....shouldnt oracle do the same
> > > > (devide the join and then bring it together)?????
> > > >
> > > > thx in advance....siad
> > > >
> > > > Sent via Deja.com
> > > > http://www.deja.com/
> > >
> > >
> >
> >
> > Sent via Deja.com
> > http://www.deja.com/
>
>

Sent via Deja.com
http://www.deja.com/ Received on Wed Jan 03 2001 - 17:28:51 CST