On Wed, 2006-03-15 at 18:09, Abbath wrote:
> Hello Scott,
>
> Wednesday, March 15, 2006, 8:49:00 PM, you wrote:
> >>
> >> I can't guess what the user want to search.
>
> > But that query will likely load up all the index info into memory.
>
> Misunderstanding: I experienced that if I run a sear
Hello Scott,
Wednesday, March 15, 2006, 8:49:00 PM, you wrote:
> On Wed, 2006-03-15 at 13:36, Abbath wrote:
>> Hello Richard,
>>
>> Wednesday, March 15, 2006, 3:35:26 PM, you wrote:
>> > If you want to force the data to be cached, just put a cron-job in to
>> > run a query for "abc" or whatever
On Wed, 2006-03-15 at 13:36, Abbath wrote:
> Hello Richard,
>
> Wednesday, March 15, 2006, 3:35:26 PM, you wrote:
> > If you want to force the data to be cached, just put a cron-job in to
> > run a query for "abc" or whatever once a minute.
>
> I can't guess what the user want to search.
But tha
Hello Richard,
Wednesday, March 15, 2006, 3:35:26 PM, you wrote:
> Abbath wrote:
>> is slow for the first time (7-15 sec), but then using the same keyword
>> next time it is fast (10-100 ms). The reason is, as I read, first time
>> it is not cached at all, but next time the index pages are
>> cac
Abbath wrote:
is slow for the first time (7-15 sec), but then using the same keyword
next time it is fast (10-100 ms). The reason is, as I read, first time
it is not cached at all, but next time the index pages are
cached so it is fast.
I think in a real word application, in this form, it is use
