Hi,
I can confirm that version 2.9.1347 works well.
Monitoring ~110k files, the nxlog process does not go above 510MB RAM.
I don't know if it help anybody, but that's with two file sources and using
Recursive TRUE
PollInterval 30
DirCheckInterval 120
ActiveFiles 4
CloseWhenIdle TRUE
Thanks.
On Mon, Mar 30, 2015 at 3:28 PM Andrei-Florian Staicu <
andrei.sta...@gmail.com> wrote:
> Cool, thanks for the info. I'll wait for that release then.
>
> On Mon, Mar 30, 2015 at 3:26 PM Botond Botyanszki <b...@nxlog.org> wrote:
>
>> Hi,
>>
>> This should be solved in 2.9.1347.
>>
>> Regards,
>> Botond
>>
>> On Mon, 30 Mar 2015 12:12:17 +0000
>> Andrei-Florian Staicu <andrei.sta...@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > Does anyone have a link for downloading nxlog 2.7.1189? I'd like to see
>> if
>> > the issue in this thread reproduces on that version, but all i can find
>> are
>> > downloads for the current 2.8.1248
>> >
>> > Thanks.
>> >
>> > On Thu, Mar 5, 2015 at 5:32 PM Botond Botyanszki <b...@nxlog.org>
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > Thanks for reporting this. There must be some regression here, as far
>> as
>> > > I remember it used to be ok with a large number of files.
>> > >
>> > > There is a 64K buffer for each input (i.e. file) which should be only
>> > > allocated for files in the active set and it gets released when the
>> file
>> > > is closed. For some reason this does not happen, needs to be
>> investigated
>> > > further...
>> > >
>> > > Regards,
>> > > Botond
>> > >
>> > > On Wed, 04 Mar 2015 13:25:50 +0000
>> > > Andrei-Florian Staicu <andrei.sta...@gmail.com> wrote:
>> > >
>> > > > Hi all,
>> > > >
>> > > > I've been trying to use nxlog in conjunction with an ELK setup.
>> > > > We have an IIS "cluster" (as in not Windows cluster, but several
>> load
>> > > > balanced IIS instances), serving a number of sites. As the logs
>> > > > accumulate (1 file/hour), and there's usually no need to remove old
>> > > > logs, the files just accumulate there.
>> > > > I tried monitoring two of the IIS log folders (see nxlog config
>> here:
>> > > > https://gist.github.com/smarmie/58b213e9f336773c6b4c ), each
>> having ~8k
>> > > > files, and the nxlog.exe process eats ~520MB RAM already at startup.
>> > > > Do you think this is a normal behavior? The configcache.dat file
>> that
>> > > > tracks all these is only 1.25MB.
>> > > >
>> > > > Thanks.
>> > >
>> > > ------------------------------------------------------------
>> > > ------------------
>> > > Dive into the World of Parallel Programming The Go Parallel Website,
>> > > sponsored
>> > > by Intel and developed in partnership with Slashdot Media, is your
>> hub for
>> > > all
>> > > things parallel software development, from weekly thought leadership
>> blogs
>> > > to
>> > > news, videos, case studies, tutorials and more. Take a look and join
>> the
>> > > conversation now. http://goparallel.sourceforge.net/
>> > > _______________________________________________
>> > > nxlog-ce-users mailing list
>> > > nxlog-ce-users@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
>> > >
>>
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
