The performance of NotificationOriginator::generate

[Frank Fock]

Hi Robert,

The NotificationOriginator::generate function is indeed
very complex. It checks the SNMP-TARGET-MIB *and* the
SNMP-NOTIFICATION-MIB for targets and notification filters
before it sends a notification.

But even if it is able to send 100 notifications in 44
seconds on your platform (which seems in fact to be slow),
I would not consider that as a bottle neck, because a
manager application cannot process that amount of
notifications in a reasonable way. That is especially
true, when considering, that a manager application in
a real world scenario, manages more than one agent!
Consequently, you should try to minimize the number
of notifications sent by the agent.

Best regards,
Frank

(Please consider also possible UDP buffer overflows
at the notification target destination)


Robert wrote:
> Hi, Jochen
> 
> I find that the performance of Agent to send notification is very low.
> After some processing , I call the NotificationOriginator::generate() to send a notification. I found it is very slow. So I try to comment that function to test it again. It become very quickly.
> For example, it takes 44 seconds to send 100 notifications.
> But it only take 8 seconds to send the same number after commenting that function and adding a debug sentence.
> So this function become a bottleneck of Agent.
> What can I modify the NotificationOriginator::generate() to improve the performance ?
> 
> Best regards,
> Robert
>