tags:

views:

139

answers:

2

I've noticed that in a file search (CTRL+H) in Eclipse, the first time you search against a "Working Set" it takes a considerable amount of time for the search to complete. Subsequent searches on that Working Set run much faster, presumably because there is some sort of index it is searching against rather than the actual files. However, after a (un)certain amount of time that indexing seems to expire and the search routine reverts back to the full file parsing.

What is the lifetime of this cached indexing? Can it be increased or persisted?

+1  A: 

I believe that this is OS-level caching in effect. Eclipse itself doesn't cache your files when searching via CTRL-H.

Peter Štibraný
A: 

Wow, thats is really bad. I DON'T want eclipse to hog my filecache: if I only search one time I dont want everything ELSE to be slow. :(

I sometimes search through tens of thousands of files.

sandos