Hello,

there is a home-made collector processing files (via SAMBA mount) .
Total number of lines is about 20 000 000 and final effective
performance is about 990 Events (lines) per second. Cutstomer complains
such result and expects it to be imporoved.

I performed some testings and results are following:
- when rejecting all events, the "performance" is about 7900 EPS
- when accepting all lines without any additional processing, we have
2884 EPS

Well, above numbers say how fast is the hardware used there, but ...

- when requied processing logic was enabled, perfomance stepped down to
911 EPS but after simple optimization steps *we achieved 991 EPS which
is still not acceptable.
*
To be more precise, main body (parse method) calls 4 map lokups (18,
154, 81 and 151 lines). As I guess these operation are key ones in terms
of performance.
MY QUESTIONS:
- IS THE \"LOOKUP\" FUNCTION PROVIDED WITH SDK ALREADY OPTIMIZED (BINARY
SEARCH, BST ETC?) OR SHOULD BE REPLACED BY SOMETHING ELSE, E.G. OWN
WRITTEN?

- ANY OTHER IDEAS HOW TO INCREASE PERFORMANCE (PLEASE, DON'T OFFER
HARDWARE UPGRADE :-)


Regards, Dariusz


--
karakan
------------------------------------------------------------------------
karakan's Profile: https://forums.netiq.com/member.php?userid=10087
View this thread: https://forums.netiq.com/showthread.php?t=54462