Larry,
There were several enhancements since 2.3 regarding this, you should
check with the latest release. Let me know if the issue persists with
this. Also PollInterval and DirCheckInterval could be increased to trade
in some CPU (in case of a lot of files) for being less real-time.
Regards,
Botond
On Thu, 3 Apr 2014 10:59:50 -0400
"Ciummo, Lawrence" <lawrence.ciu...@emc.com> wrote:
> I have a large app that uses log4cplus to create a log file for each disk
> drive on a system - about 1000 files. We use nxlog to transfer files to a PC
> during testing. (conf file fragment below).
>
> It appears, with about 1000 files in the monitored directory, we take a 5%
> performance hit overall. I haven't pinned it down to nxlog yet, but I did
> see some notes in the latest release of nxlog that mentions wildcards
> monitoring. There is very little writing to these files, as they are used
> for exception logging only - maybe 1-2 writes to each file at the beginning
> of a 2 hr test run.
>
> I'm currently using 2.3.1027.
>
> Thanks
> Larry
>
>
>
>
>
> # Drive logs and their rollovers
> #
> <Input drives_in>
> Module
> im_file
> File
> "/logs/drive/*"
> # Get the position from the file name
> # Exec $base_file = file_name();
> # Extract out position "drive_PPPPPPPP.log" - extract PPPPPPP
> #Moved to receiver side
> # Exec if $base_file =~ /^.*drive_(.*)\.log.*$/ \
> # $pos = $1; \
> # else $pos="unknown";
> Exec $raw_event = "<<" + file_name() + ">>" + $raw_event;
> # Exec log_info(" Record: " + $raw_event );
>
------------------------------------------------------------------------------
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
