Diogo Biazus wrote:
Bill Moran wrote:
Diogo Biazus wrote:
Hi folks,
Does anyone has an idea of a more cost eficient solution?
How to get a better performance without having to invest some
astronomicaly high amount of money?
This isn't hardware related, but FreeBSD 5 is not a particularly
impr
Wednesday, March 31, 2004 10:30 AM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Wich hardware suits best for large
> full-text indexed databases
>
>
> Dann Corbit wrote:
>
> >Can we see the underlying tables also?
> >
> >
> CREA
Dann Corbit wrote:
I see that only table documentos has a unique index. Is it really so
that none of the other tables has a key to uniquely identify a record?
Perhaps the others have a unique attribute but it was never declared
when forming the index?
I thougth that a primary key would create
> -Original Message-
> From: Diogo Biazus [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 31, 2004 11:02 AM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Wich hardware suits best for large
> full-text indexed databases
>
>
> Dann
explain SELECT qrydocumentos.coddocumento, qrydocumentos.nomedocumento,
qrydocumentos.conteudo, qrydocumentos.tamanho, qrydocumentos.hora,
qrydocumentos.data, qrydocumentos.codfonte, qrydocumentos.nomefonte,
qrydocumentos.numeroimagens as "numeroImagens", qrydocumentos.subtitulo,
qrydocumentos.
Look into running Swish-e instead:
http://www.swish-e.org
Great speed, nice engine, excellent boolean searches. We run it on
several sites each with over 500,000 documents. Performance is
consistently sub-second response time, and we also integrate it within
PHP, Perl and Postgresql too.
I know
Diogo Biazus wrote:
Hi folks,
I have a database using tsearch2 to index 300 000 documents.
I've already have optimized the queries, and the database is vacuumed on
a daily basis.
The stat function tells me that my index has aprox. 460 000 unique words
(I'm using stemmer and a nice stopword list)
Can we see the schema for the table qrydocumentos ?
-Original Message-
From: Diogo Biazus [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 30, 2004 2:32 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] Wich hardware suits best for large full-text
indexed databases
Dann
Dann Corbit wrote:
What does the EXPLAIN command say about the slowest queries?
explain SELECT qrydocumentos.coddocumento, qrydocumentos.nomedocumento,
qrydocumentos.conteudo, qrydocumentos.tamanho, qrydocumentos.hora,
qrydocumentos.data, qrydocumentos.codfonte, qrydocumentos.nomefonte,
> -Original Message-
> From: Diogo Biazus [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 30, 2004 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: [GENERAL] Wich hardware suits best for large
> full-text indexed databases
>
>
> Hi folks,
>
> I have a dat
Hi folks,
I have a database using tsearch2 to index 300 000 documents.
I've already have optimized the queries, and the database is vacuumed on
a daily basis.
The stat function tells me that my index has aprox. 460 000 unique words
(I'm using stemmer and a nice stopword list).
The problem is per
11 matches
Mail list logo
