From: "Vladimir M. Zakharychev" <bob@dpsp-yes.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Performance
Date: Mon, 9 Sep 2002 21:15:37 +0400
Organization: N-Networks
Lines: 67
Message-ID: <alil0c$543$1@babylon.agtel.net>
References: <bV3f9.10197$_J3.409715@news0.telusplanet.net> <u04f9.259894$aA.44922@sccrnsc02> <tm4f9.10209$_J3.414519@news0.telusplanet.net>
NNTP-Posting-Host: 212.233.81.44
Mime-Version: 1.0
Content-Type: text/plain;
 charset="windows-1251"
Content-Transfer-Encoding: 7bit
X-Trace: babylon.agtel.net 1031591756 5251 212.233.81.44 (9 Sep 2002 17:15:56 GMT)
X-Complaints-To: usenet@babylon.agtel.net
NNTP-Posting-Date: 9 Sep 2002 17:15:56 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000


Well, it takes time to just fetch and display all those 17k rows with 60
columns in each. I don't see any reason for a client application to
retrieve the whole dataset and work with it locally, but if your application
works this way, be prepared for very heavy network traffic and very bad
performance - as I said, it takes time (and a lot) to just send all data to
client and your experiment shows nothing about how quickly Oracle was
able to start sending you rows (which was "immediately" since you
requested trivial full table scan).

--
Vladimir Zakharychev (bob@dpsp-yes.com)                http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.


"Lucas" <Lucas_44@hotmail.com> wrote in message news:tm4f9.10209$_J3.414519@news0.telusplanet.net...
> Ok, I was a little vague.
> Win2000
> P3 900 mhz
> 384 RAM
> Oracle 8 , testing on local machine only, not even on server with concurent
> users.
>
> I'm trying to optimize our db, I'm testing our SQL calls and seeing if
> indexing would help speed up the program. We can retreive records from
> different
> levels in the program, the higher the level the more records. I tried a
> straight call (select * from table), it has 60 fields, 17,000 recs and it
> took close to 1 min
> to get all the rows. This is from SQL*Plus, so obviously in a program with
> user interface, getting all the record plus all the lookups makes it ever
> slower. The fields
> are basic varchars, integers, couple of varchar2(255), 1 longraw with hardly
> any images in it.
>
> Lucas
>
>
>
>
> "Michael J. Moore" <hicamel_x_the_spam@attbi.com> wrote in message
> news:u04f9.259894$aA.44922@sccrnsc02...
> > With the small amount of information you have given, I'd say that
 generally
> > you are right, that's pretty darn slow.
> > But if you are running on Win95, with 500 concurrent users, and your
 columns
> > are imbedded tables or clobs,
> > maybe that is totally reasonable. You really need to give a lot more
> > information for anybody to make the kind of assessment you are looking
 for.
> >
> > "Lucas" <Lucas_44@hotmail.com> wrote in message
> > news:bV3f9.10197$_J3.409715@news0.telusplanet.net...
> > > With just a basic (select * from ATable ) that has 60 fields and 17,000
> > > records it takes close to 1 min to retrieve all the row, seems slow to
 me?
> > > Or am I expecting too much?
> > >
> > > Lucas
> > >
> > >
> >
> >
>
>


