Dmitri Kovalsky wrote:

> ----- Original Message -----
> From: "Alexander F Avdonkin" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, May 14, 2002 12:01 PM
> Subject: Re: [aseek-users] Memory utilization and scalability
>
> > Dmitri Kovalsky wrote:
> >
> > > I have 13G binary database and 33G MySQL database, and I got two
> problems:
> > > - index -D always says mysql server is gone away, but I have mysql
> > > configured using my-huge.cnf, with hundreds of megs for primary keys and
> > > buffers.
> > >
> >
> > Which version of ASPseek and MySQL are you using ?
>
> I am using MySQL 3.23.41 and ASPseek 1.2.8, gradually upgraded
> from 1.2.6
>

Strange, do you use "IncremetalCitations yes" and "CompactStorage yes" ?

>
> Best Regards.
> Dmitri Kovalsky
>
> >
> > >
> > > - searchd always consumes 1.5G of RAM
> >
> > On start searchd consumes at least MAX_URL_ID * 4  bytes. Recently we
> found
> > two memleaks in searchd.
> > Take latest CVS version.
>
> I will try it, it would not broke sql or binary databases?

No


>
>
> >
> > >
> > >
> > > My machine is Dual 1Ghz pentium III with 2Gb of RAM running RedHat 7.2
> with
> > > latest updates.
> > > So what I'd like to know, if, firstly I got something messed up or I
> just
> > > need more horsepower, and secondly, about searchd, is it ok or I should
> buy
> > > more RAM?
> > >
> > > Also, what is the best way to use more than one machine for aspseek?
> > >
> > > Best Regards,
> > > Dmitri
> >
> >
> > --
> > www.Argentina.com
> > E-mail Profesional y Acceso a Internet UltraVeloz totalmente GRATIS en
> > Buenos Aires, Rosario, Cordoba, Mendoza, La Plata y Pilar
> >
> >

Reply via email to