[HAPI-devel] Hapi parse performance.

[Mike M. <mi...@th...>]

Hi,

Are the any efforts being made to improve the performance of parsing an hl7
message?

I am considering dropping parsing of messages using hapi because of the CPU
load and memory requirements.

It seems like Hapi parses like a DOM parser as it goes though the entire
message.

It would be good if the message was lazily parsed so that no parsing occurs
until a teaser.get call is made, or an accessor called on the concrete
message object returned from parse(). When the terser path is executed only
the required segment/group/field/sub fields are processed to retrieve the
desired value.

That way, if we wanted just the MSH9-2 the copy expense of parsing an
entire message is not required.

My initial performance testing indicates that the JVM dropped from 10% CPU
usage with Hapi to 3% CPU usage when using string.split().

Are there efforts being made to address the performance of Hapi?

Kind regards.

Mike