fts- contains expression: slow the first time fast the other time

I have a table with 1,500,000 name and first name
I use Full text search on name and first name
when I use a contains expression like
select ... from table1 where contains( name,'abc') the query take 45 secs
immediatly after this test I search for the same or another name and the
query take under 1 secs ...
an hour later app.. I run the same test and the first query take 45 secs again
I try a test with search 1,000,000 different name ( for validate if the
problem was the caching )... the first on take 45 secs app and the 999,999
others case take under 1 secs
on my local computer all search run under 1 secs
Peter Yang from microsoft private news groups think that is a memory
(cache) problem... !!! but I think 45 secs is too high for a single unique
key search in link with a cache problem
could you help me ?
Which microsoft private newsgroup would that be. You should dedicate a
minimum of 1 Gig to your OS, so cap your max sql memory at physical - 1 Gig.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"OLAPFOREVER" <OLAPFOREVER@.discussions.microsoft.com> wrote in message
news:D0557CFF-B262-441F-9ADD-7E0E82DE8283@.microsoft.com...
>I have a table with 1,500,000 name and first name
> I use Full text search on name and first name
> when I use a contains expression like
> select ... from table1 where contains( name,'abc') the query take 45
> secs
> immediatly after this test I search for the same or another name and the
> query take under 1 secs ...
> an hour later app.. I run the same test and the first query take 45 secs
> again
>
> I try a test with search 1,000,000 different name ( for validate if the
> problem was the caching )... the first on take 45 secs app and the
> 999,999
> others case take under 1 secs
> on my local computer all search run under 1 secs
> Peter Yang from microsoft private news groups think that is a memory
> (cache) problem... !!! but I think 45 secs is too high for a single
> unique
> key search in link with a cache problem
> could you help me ?
>