[SNMP4J] Query on MOServerLookupListener queryEvent() API

[Frank Fock]

Hi Vikram,

You have two options to improve the performance:
1. Do not update the table for each request. Instead use a timeout (e.g. 
5 seconds).
2. Use a timeout on row level and fetch only the those rows that will be 
potentially
reached by the request when takin gmaxRepetitions for GETBULK requests 
into account.
3. Implement your own MOTableModel which fetches the rows on demand 
(from the
tailIterator which is called by DefaultMOTable). At the same time, 
existing rows (i.e.
cached rows) have to be updated and non-used rows have to be removed without
interfering concurrent requests.

Option 3 is the most complex but also most efficient solution.
I will provie such a MOTableModel with SNMP4J-Agent 3.0 later this year.

Hope this helps.

Best regards,
Frank


Am 19.02.2014 09:02, schrieb VIKRAM MODUGU:
> Hi,
>
> We have requirement for the snmp4j project.
>
> Our Implementation:
>
> We have a requirement for bulk snmp request for our snmp4j agent for a particular snmp table.
> For this requirement we have implemented MOServerLookupListener interface and registered the class with the SNMP agent.
> In MOServerLookupListener implementation we retrieving the content for the snmp table from a database table which is having very bulk data(say 20,000 records). My client is issuing the get next request for each entry inside the table.
>
>
> Problem:
>
> For each Get-Next request we are retrieving all the 20, 000 records from the database, this is the overhead we have. Do we have a better solution than this?
>
> Your help is appreciated in this regard.
>
> PFA listener class implementation for your reference.
>
> Thanks,
> Vikram Modugu.
>
>
>
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j

-- 
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax:   +49 7024 8688231