On Wed, Jun 12, 2002 at 08:28:27PM +0500, Alexander Barkov wrote:
> What does "mysqladmin processlist" display?
>
> Are there any active queries being executed by
> mnogosearch?
Well, I switched the query logging on. In the query log file I can see:
$ ./indexer -Cw -t "ECA" &
$ tail -f /var/log/mysqld.log
020613 10:55:26 4 Connect mnogosearch@localhost on mnogosearch
4 Query SELECT rec_id FROM url WHERE rec_id<>0
AND (url.tag LIKE 'ECA') LIMIT 128
4 Query DELETE FROM ndict2 WHERE url_id
in
(76815,76816,76817,76818,76819,76820,76821,76822,76823,76824,76825,76826,76827,76828,76829,76830,76831,76832,76833,76834,76835,76836,76837,76838,76839,76840,76841,76842,76843,76844,76845,76846,76847,76848,76849,76850,76851,76852,76853,76854,76855,76856,76857,76858,76859,76860,76861,76862,76863,76864,76865,76866,76867,76868,76869,76870,76871,76872,76873,76874,76875,76876,76877,76878,76879,76880,76881,76882,76883,76884,76885,76886,76887,76888,76889,76890,76891,76892,76893,76894,76895,76896,76897,76898,76899,76900,76901,76902,76903,76904,76905,76906,76907,76908,76909,76910,76911,76912,76913,76914,76915,76916,76917,76918,76919,76920,76921,76922,76923,76924,76925,76926,76927,76928,76929,76930,76931,76932,76933,76934,76935,76936,76937,76938,76939,76940,76941,76942)
4 Query DELETE FROM ndict3 WHERE url_id
in
(76815,76816,76817,76818,76819,76820,76821,76822,76823,76824,76825,76826,76827,76828,7682
...
(many lines deleted)
with the heavy disk I/O activity. Now, this does not look like very efficient
implementation, does it? Everything works very slow, indexer obviously
executes enormous number of queries in order to accomplish simple(?) task
of deleting all entries which correspond to a certain tag. Which points
to the fact that certain trade-offs were made regarding search speed
vs. update speed.
However, what concerns me more is that the whole process
died after three hours without finishing the task. I wonder how much
is the setup with multiple dictionaries tested with higher number of URLs?
Which possible mysql tuning parameters would you recommend in order
to speed up the deletion process? Is it so that during the
deletion process indexer stores the state variables internally which
then grow with the number of URLs which are to be deleted?
best regards,
Kresimir
>
>
> Kreso wrote:
> > RedHat 7.2, 2x1Ghz, 512MB, hardware RAID dedicated search maschine,
> > no other tasks running. MySQL 3.23.49, default configuration. Maybe
> > some mysql tuning would help. Unfortunately, indexer has terminated
> > after 3 hours, without doing its job. It seems like a bug to me. Are
> > there any known limitations on database size, i.e. on the number
> > of URLs that can be indexed?
> >
> > thanks again,
> > Kresimir
> >
> >
> > On Tue, Jun 11, 2002 at 06:21:22PM +0500, Aleksey Trubin wrote:
> >
> >>Kreso wrote:
> >>
> >>
> >>>Hallo,
> >>>
> >>>I have a problem with indexer -Cw -t "xxx". It takes too much time.
> >>>With a database 1.5 million entries it works longer than 2 hours already.
> >>>mysqld doesn't take much CPU. Any ideas? mnogosearch v3.1.19 is in the
> >>>question. I have created an index on tags before.
> >>>
> >>>thanks,
> >>>Kresimir
> >>>___________________________________________
> >>>If you want to unsubscribe send "unsubscribe general"
> >>>to [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>So... It can depends on many things.
> >>What is your OS, what tasks are executing on the server, mysql version?
> >>
> >
> > ___________________________________________
> > If you want to unsubscribe send "unsubscribe general"
> > to [EMAIL PROTECTED]
> >
> >
> >
>
>
>
> ___________________________________________
> If you want to unsubscribe send "unsubscribe general"
> to [EMAIL PROTECTED]
___________________________________________
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]
