Hi all,
I am sorry, I have made a mistake.
The flag NETSNMP_ITERATOR_FLAG_SORTED does work under net-snmp 5.2.1. Every
request goes through get_first_data_point and a series of get_next_data_point
without this flag, and the number of get_next_data_point is the row number.
But there still have performance issue when the row number is very very large,
which is up to 20k. Because it still needs to go through a large number of
get_next_data_point.
发件人： xinyilong
发送时间： 2014-06-23 12:35
收件人： net-snmp-coders
主题： [SOS] How to improve table-iterator's performance when the table is huge?
Hi all,
My net-snmp's version is 5.2.1. When the table is huge, which is up to 20k
rows，the table-iterator is very very slow.
I have check the flow, as below:
when it gets the first row, it uses get_first_data_point, and when it gets the
second row, it uses get_first_data_point and then get_next_data_point. So when
there is many many rows, it uses a get_first_data_point and a series of
get_next_data_point.
The performance is very very bad and I can not afford it. I have used the flag
NETSNMP_ITERATOR_FLAG_SORTED, but it does not work yet.
Is there some other modes than table-iterator, which have good performance
under huge table?
陇昕翼 A-01
Skype : lxyscls Mobile phone : 13198525721
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
