Agentless User ID - Server Log Monitor Frequency

[herrmoss]

After configuring Agentless User ID, the default value for Server Log Monitor Frequency of 2 seconds caused CPU usage on the Domain Controller to be higher than desired.  Changing this value to 10 seconds brought CPU usage on the Domain Controller to an acceptable level.  What are the ramifications of having this longer Server Log Monitor Frequency?

[bpeeri]

In our testing the user-ID agent running on windows box will reduce CPU usage .

We sow only 3% increase using user-ID agent .

Also see this refferece; here   (Page 13) . 

[reaper · Accepted solution]

The longer the time between log reads, the longer a user may potentially be blocked from accessing resources

If a user logs on to his device the second after a log read ocurred, UserID will not be aware of this account for another 9 seconds. Any security policy requiring a UserID will not be available for the next 9 seconds. For the average user activity this will probably not have big consequences, as a user tends to boot up and launch 'slower' applications first. Any startup scripts launched at startup may be blocked by policyhowever as they trigger the moment a user is logged in

[herrmoss]

Thanks reaper.  I suspected that was the case but wanted someone to verify that I wasn't crazy.