Re: [SQL] Performance

From: Karl Denninger <karl(at)Denninger(dot)Net>
To: Jason Slagle <raistlin(at)tacorp(dot)net>, Tim Perdue <perdue(at)raccoon(dot)com>
Cc: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, pgsql-sql(at)hub(dot)org
Subject: Re: [SQL] Performance
Date: 1999-03-10 03:30:40
Message-ID: 19990309213040.A16905@Denninger.Net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


Build appropriate indices for the fields you intend to discriminate on
during a SELECT.

200MB is SMALL. I used to run searches over 10G of data in under 2 minutes
looking for RADIUS detail records. The trick is to build the right set of
indices for what you intend to be querying on.

--
--
Karl Denninger (karl(at)denninger(dot)net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.

> What, if anything, are you using as an index.
>
> I have 1,400,000 entries (200MB) I'm inserting into a database. Radius
> detail files as a matter of fact. Apart from COPY taking forever to load
> that (probably due to my several indexes), it seems the select is VERY
> slow. Any tips?
>
> How CPU intensive is a select?
>
> Jason
>
> ---
> Jason Slagle
> Network Administrator - Toledo Internet Access - Toledo Ohio
> - raistlin(at)tacorp(dot)net - jslagle(at)toledolink(dot)com - WHOIS JS10172
>
> On Tue, 9 Mar 1999, Tim Perdue wrote:
>
> > It searches the bodies, not the subjects or authors. I don't see why anyone
> > needs to search for a particular author. But if it's requested enough, it
> > would be trivial to implement.....
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: D'Arcy J.M. Cain <darcy(at)druid(dot)net>
> > To: perdue(at)raccoon(dot)com <perdue(at)raccoon(dot)com>
> > Cc: pgsql-sql(at)hub(dot)org <pgsql-sql(at)hub(dot)org>
> > Date: Tuesday, March 09, 1999 9:10 PM
> > Subject: Re: [SQL] Performance
> >
> >
> > >Thus spake Tim Perdue
> > >> Some time back I sent out a message asking if PGSQL would be able to
> > handle
> > >> my mailing list archive at http://www.geocrawler.com/ , and whether it
> > would
> > >> scale up to 100MB.
> > >
> > >Cool. We now have a searchable archive for PostgreSQL. However, I
> > >tried a search and it didn't seem to work. In pgsql-hackers I entered
> > >"niladic" (I tried "Niladic" just in case) and it failed to find any
> > >messages, even though I could see a few on the list of recent messages.
> > >Any ideas?
> > >
> > >--
> > >D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
> > >http://www.druid.net/darcy/ | and a sheep voting on
> > >+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
> >
> >
>
>

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tim Perdue 1999-03-10 03:33:57 Re: [SQL] Performance
Previous Message Jason Slagle 1999-03-10 03:24:05 Re: [SQL] Performance