Slow for large parts

[ianxm]

For large parts (over 10k) this slows down. I extended the ParserTest to 20k and the TinkParser test takes over 10 seconds. My machine is old but 10 seconds is a lot. This is using hashlink. Is this expected? Is it meant to be done differently for larger payloads?

[back2dos]

Well, tink libs run the risk of performing poorly on HL, because HL's GC is for example not generational, and tink assumes that short lived objects are cheap (as they are on most targets). But this definitely seems excessive.

I must admit, I've only build prod servers with node and php, where for the former one would use BusboyParser and for the latter it's handled by php. So I can't really say how good the TinkParser is. Still 10s for a 20k chunk should be easy to improve upon ^^