Hi All !
I am fighting with watching a large amount of files for their content
and look for some keywords, which indicate dangerous error situations to
me. This costs me currently hours each day.
I know, how to use the FileSystemWatch er class. But in my case, I would
like to open about 500 files and watch each of them for progress/enlarge
by the creating process. If the recognized addendum to the file contains
my keyword, I would write it to a logfile or take any other action. Not
too complicated.
But what about the system-resources? The files are up to 500 MB in size
and I could expect to have 20 to 50 changes per second.
For the files, I can keep the buffers small [which is only a problem in
intial read-through], so that I do not occupy too much memory. But how
many FileSystemWatch ers can I create and will so many work solid? I
would working local on the server, FileSystemWatch er events are not too
solid over the wire.
Any thoughts are really very welcome!
Thanks so far and
best regards,
Manfred
I am fighting with watching a large amount of files for their content
and look for some keywords, which indicate dangerous error situations to
me. This costs me currently hours each day.
I know, how to use the FileSystemWatch er class. But in my case, I would
like to open about 500 files and watch each of them for progress/enlarge
by the creating process. If the recognized addendum to the file contains
my keyword, I would write it to a logfile or take any other action. Not
too complicated.
But what about the system-resources? The files are up to 500 MB in size
and I could expect to have 20 to 50 changes per second.
For the files, I can keep the buffers small [which is only a problem in
intial read-through], so that I do not occupy too much memory. But how
many FileSystemWatch ers can I create and will so many work solid? I
would working local on the server, FileSystemWatch er events are not too
solid over the wire.
Any thoughts are really very welcome!
Thanks so far and
best regards,
Manfred