Please look at the top or vmstat output to find the bottleneck. Also, how many threads do you run index with? (-N parameter) BTW this discussion really belongs to aseek-users@, so I move it to this list (hope you are subscribed to aseek-users@). Fredy Kuenzler �����(�): > > >> I found that index is eating up too much server performance > (v.1.2.3). > >> Apache on the same machine (PIII 866, 256 MByte RAM) slows down > >> significantly, especially when a page contains MySQL Queries. As > soon > >> as index is stopped, everything runs in normal speed again. > > > >What is your MySQL key_buffer_size? If you don't know, you probably > haven't > >tune it yet. If so, read FAQ. > > I did as requested. mysqld --help shows: > > key_buffer_size current value: 67104768 > > Before key_buffer_size was 8M (default value). > > However, no success. While index is running, apache on the same > machine cannot deliver mysql-query-based pages in a reasonable > time-frame. > > BTW I have mysql version 3.23.36 running. > > Also I think that minDelay of apseek.conf: has no effect while > indexing. At least not like -p [n]. Obviously minDelay must be set > between each Server command. > > Thanks and regards > Fredy -- [EMAIL PROTECTED] http://kir.sever.net ICQ 7551596 -- Bend the facts to fit the conclusion. It's easier that way. -- |_ | |\| |_| >< -- |_| |\| | >< -- | ) |\/| --
