You are viewing limited content. For full access, please sign in.

Question

Question

Full Text Search Memory Requirements

asked on January 31, 2024

The Hardware Planning and Specifications document recommends at least12GB of memory for the full text search engine. But we have found it can be anywhere from less than a GB up to 64GB depending on how much text data there is.

Is there something more useful to give an estimate of how much memory should be allocated for different amounts of text data?

0 0

Replies

replied on February 2, 2024

Actually, it depends, as you know, LFFTS handles different operations when it runs, such as index, search, optimize, etc. The amount of memory needed for each of these depends on the characteristics of the content provided by the user. For example, the kind of files in the repository, the length of the word in the file, the repetition rate of the word, and the chronological order of the index, etc. All affect LFFTS‘s memory usage.

 

A more practical thing to do is to set the memory upper limit for LFFTS according to the actual hardware conditions; the more memory LFFTS uses, the better performance it will provide. Set an objective memory limit for LFFTS so that it can use this memory for caching.

 

To set the limit, open the command prompt and navigate to C:\Program Files\Laserfiche\LFFTS. Run the following command

lfftscfg.exe mem <limit>

where <limit> is the maximum amount of memory (in bytes) that LFFTS can use. For example, running

lfftscfg.exe mem 5000000000

would limit LFFTS to using no more than 5 GB of memory.

1 0
replied on February 5, 2024 Show version history

We would be more interested in allocating the amount of memory it wants to use, rather than limit functionality. Memory prices have dropped dramatically over the years.

Last I discussed limiting memory we found 2 major issues. The limit was more of a target and not guaranteed and the limit only applied to the memory used by the process, not the mapped file, which is 80-90% of it's actual committed memory draw.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.