[SNMP4J] Slow performance of SMI-POR when running under the Java Debugger (SMI-PRO 1.9.0)

[Frank Fock]

Hi Reuben,

The SMIParser.jj_scan_token() method is the scanner of the tokeniser. That is where the most work is done. So that is not surprising. It is a JavaCC generated method and pretty optimised. 

I would therefore rather optimise the debugger than trying to tune the SMI scanner.

Hope this helps anyway.

Best regards,
Frank 


> On 6. Oct 2017, at 20:32, Reuben Sivan <RSivan at advaoptical.com> wrote:
> 
> It takes me about two minutes to compile 200 MIB SMI files in debug mode, and about 10 seconds with no debug.
> 
> Running with JVisualVM I see most of the time is spent on SMIParser.jj_scan_token().
> 
> I’ll appreciate any suggestions.
> 
> 
> -- Reuben Sivan
> 
> 
> 
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> https://oosnmp.net/mailman/listinfo/snmp4j