DROID initialization time

[Gary McGath]

I've found in testing FITS that the creation of a
BinarySignatureIdentifier from the signature file is a very
time-consuming operation. I've made it a static object, so it only has
to be invoked once per run, but if users run FITS on just one file at a
time, DROID will make it extremely slow.

I've looked into serializing and caching the BinarySignatureIdentifier,
but it doesn't appear designed to be serializable. Would anyone have any
thoughts on how to get around this performance issue, either by better
utilizing the existing version of DROID or by some changes that might
happen in a future version?

--
Gary McGath ga...@mcgath.com

[Matt Palmer]

Hi Gary,

When I find the time to finish testing and release byteseek 2.0, I'm hopeful that it will be faster than the current byteseek. I have replaced the ANTLR parser with a custom parser and made a number of other optimisations. I haven't tried it in DROID yet. It won't be a drop in replacement though.

I may investigate making the core search and match objects serializable too. Any chance you can run binary signature identifier through a profiler and let me know which bits are taking the most time?

Matt

Matt