Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/969
@kevin91nl Thanks for the submission! I really do appreciate the clarity of
your code and explanations.
> Performance A ChainParser does not need to interpret a language the way
Stellar does. We found that interpreting a language was a performance
bottleneck in the parsers. In fact, we implemented a lightweight template
engine in one of our links, but that was breaking the throughput rate of the
parsers. Therefore, we removed this mechanism.
Can you elaborate on the performance bottleneck that you experienced?
I have tested this myself and found little to no performance difference
between the execution of something written in raw Java versus Stellar. I
compared doing Geo enrichments in the legacy Java adapter versus doing them
with `GEO_GET` in Stellar. I also compared doing enrichments with the legacy
HBase Java adapter versus `ENRICHMENT_GET`.
Maybe the root cause of the performance bottleneck that you experienced was
something else, a tuning issue or an unexpected problem with your template
engine? There also certainly could be a performance bug somewhere in Stellar
that I am not aware of, but I think it is reasonable to expect similar
performance between raw Java and Stellar. If we do have a performance issue
with Stellar, then I'd like to isolate and address it.
---
