Hello,
We think we have found out the reason of the memory leak, there is an
external PERL library being called that contains a call to the IdentifyFile
function to obtain the inode of windows files. Whenever this function is
called, a memory leak occurs. If we disable this call, the memory usage is
stable.
So we are thinking of a way to bypass this problem, either by using another
function or assessing if it's still needed . For that we would like to ask
you a couple of questions about SEC internal functioning when reading
(Windows) files from the file system:
1. Does SEC detect that an open file is idle, without any writing activity?
And if it does, does SEC close the file after a while, or does the file
remain open until it's explicitly closed by a process?
2. If we are processing input files using a " *" wildcard, does SEC open new
files on the fly as they are being generated?
Thanks in advance!
Natalia
------------------------------------------------------------------------------
The best possible search technologies are now affordable for all companies.
Download your FREE open source Enterprise Search Engine today!
Our experts will assist you in its installation for $59/mo, no commitment.
Test it for FREE on our Cloud platform anytime!
http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
_______________________________________________
Simple-evcorr-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
