I am not a Win user but it seems to be a memory compsumption
problem rather than a memory leak (I index more than 60000 files
with 300000 different words with no problems in Solaris but I have
2 Gb of RAM!!!).
The problem of 2.0 is as follows: It uses more memory than 1.3
while it is working in indexing mode. The reason is simple: like in
1.3 it stores all data (words, files, ...) in memory during the index
proccess but 2.0 includes a new feature (phrase search) that also
keeps in memory the positions and frequency of each word.
Perhaps, you can check with some tool (like unix top) the state of
the memory of your machine.
But as you states, if 1500 files gives you a 8 min time to index and
more than 2 hours for 4500 files, your box is clearly paging to disk.
We are working on this issue in 2.1.x (part of the info can be written
to disk with the -e option).
On 27 Nov 2000, at 6:14, Frances Coakley wrote:
> Have tried to run Swishe 2.0 (prebuilt version for Windows) - running
> on 128MByte, Windows98 2nd ed, on some 4500 files (approx 150k words
> as reported by swishe 1.3) Hangs in either removing common words (or
> if this option disabled) in writing index files (3 functions reported
> then hangs - by hang I mean processing exceeds 2hours - file read
> takes maybe 8 minutes) On a subset (1500 files, 90k words terminates
> ok after about 7/8 mins). Is this expected ? Is there any test for
> memory allocation failing ?
> However I suspect some memory leak problem even on correct termination
> as machine is then very prone to usual memory leak problems (slow
> response, blue screen, absence of icons etc) Frances Coakley Senior
> Lecturer, Rm 18BB19, Dept Elec Eng; University of Surrey, GUILDFORD,
> GU2 7XH, UK Tel +(0)1483 879129 email firstname.lastname@example.org
Received on Mon Nov 27 17:18:06 2000