-
Notifications
You must be signed in to change notification settings - Fork 66
Slow getSubtree #57
Comments
I don't think so. Can you figure what what it is that takes so long, using pcaps and debugging as appropriate? |
@leo-combes: could you specify which net-snmp command you are comparing specifically? The original getSubtree fetches only single values - while pull request #44 implements getBulkRequest, which, depending on the snmp server implementation, may give faster (or slower) response. |
@calmh I will do some additional research and confirm. @bangert You are correct, my test are made with snmpbulkwalk: snmpbulkwalk -v 2c -c public 192.168.128.6 .1.3.6.1.4.1.4998.1.1.20.2.27.1.17 Now, I do a test with "normal" snmpwalk and takes 16 seconds. |
it's not available in any release yet. i have been using the implementation in #44 for a while... |
thank you. what times do you measure now? In my experience, node-snmp-native should not be slower than the net-snmp cli tools... |
Tests over OID with 80 values, same remote host (non local, over internet): net-snmp: node-snmp-native: |
so node-snmp-native is marginally slower (~2%). thanks for correcting me on that ;-) |
Hello, first of all thanks for sharing this excellent piece of code.
In most cases, I see that the get or getAll requests are fast, a lot, comparable with net-snmp from bash.
However, now I start to try getSubtree and it works extremely slow. To compare, a particular request takes 1.8 seconds with net-snmp from bash and snmp-native takes 27 seconds. The two tests are done on the same server, against the same host and the same OID.
Is it normal for getSubtree to take so long?
The text was updated successfully, but these errors were encountered: