bnlong / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

Performance issues in Windows Server 2008 #39

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install on 2k8 
2. Observe performance when size goes above 50 megabytes

What is the expected output? What do you see instead?
Evtsys uses the EvtQuery API call in 2008, which means that it searches the 
entire log file every five seconds based on the query.  This causes massive 
performance problems.  A better solution is to use the EvtSubscribe API call to 
be notified about new events as they come in.

What version of the product are you using? On what operating system?
Latest from SVN on Windows Server 2008 R2.

Please provide any additional information below.
Here's the API doc for EvtSubscribe:
http://msdn.microsoft.com/en-us/library/aa385487%28v=vs.85%29.aspx

Original issue reported on code.google.com by mchol...@gmail.com on 13 May 2011 at 7:20

GoogleCodeExporter commented 8 years ago
Will attempt to implement the proposed solution.

Original comment by sherwin....@gmail.com on 20 May 2011 at 2:38

GoogleCodeExporter commented 8 years ago
This has been completed and is currently committed to the trunk. I have not 
tagged a release yet since I plan on adding some additional features to it.

The trunk is stable and you are free to build from it or request a build if 
you'd like to try it.

-Sherwin

Original comment by sherwin....@gmail.com on 1 Aug 2011 at 3:49

GoogleCodeExporter commented 8 years ago
Hi Sherwin,
I am running eventsys4.1, the latest version available on your site, but still 
encountering perfromance issues on Windows 2008. I wanted to check if the issue 
with windows 2008 performance has been resolved. if so, Please let me know what 
is version has resolved the issue so that I can redeploy it on all my servers. 

Original comment by surfra...@gmail.com on 27 Oct 2011 at 9:35

GoogleCodeExporter commented 8 years ago
This issue has been addressed, but no official release has been
produced as of yet. You would need to build from the trunk to get the
fix.

-Sherwin

On Oct 27, 2011, at 5:36 AM, "eventlog-to-syslog@googlecode.com"
<eventlog-to-syslog@googlecode.com> wrote:

Original comment by sherwin....@gmail.com on 31 Oct 2011 at 1:50