Network benchmark - header parsing

[Hal Snyder]

Miguel Barreiro <enano@REDACTED> writes:

> I've faced the same situation with video streaming and the Erlang
> runtime is fast enough for sending several tens of megabits of
> MPEG-2 video as Transport Streams over UDP with relatively low
> jitter.
>
> The opposite, however (receiving streams and parsing braindead
> headers such as those in MPEG PS/PES packets) involves quite a bit
> of bitsyntax matching and is relatively inefficient.

We are certainly interested in parsing headers efficiently. SIP
headers should permit the same sort of optimization that's done with
{packet,http} - in fact it doesn't look too hard to make something
general in which the header names could be loaded after startup.

What sort of header munging is the slow part for your inbound
processing?

I am favorably impressed with bit syntax performance, to put it
mildly. But, reflecting on recent mention on this list about regexes,
would a set of regexes-for-binaries ops would help speed things up?