Hi,
I recently measured some load and filter times with and without a LUA postdissector plugin called TRANSUM. I tried three different scenarios:
·
No LUA - without any plugins other than those shipped as standard
·
Bypassed LUA – with TRANSUM but a preference set so that on entry to the postdissector immediately returns to Wireshark
·
LUA Enabled – with TRANSUM enabled
The test file was a 47MB pcapng file with mostly web traffic. Almost all of the data packets would have been scrutinised by TRANSUM in some detail.
I timed loading the file and then filtering with the expresssion
tcp.len>0. The timings were:
|
No LUA
|
Bypassed LUA
|
LUA Enabled
|
Load of file
|
1.0s
|
2.5s
|
5.4s
|
Filter with tcp.len>0
|
1.7s
|
2.9s
|
5.2s
|
The thing that surprised me was the impact of just having the LUA loaded, even if it immediately returned to Wireshak (the Bypassed LUA scenario).
Not a problem – just an observation.
Best regards…Paul
Paul Offord FBCS CITP
Chief Technical Officer
Advance7
Phone: 01279 211 668
Mobile: 07764 931 431
Email: paul.offord@xxxxxxxxxxxx
LinkedIn: https://uk.linkedin.com/in/paulofford