bfb27b7caa
This is far from comprehensive, mainly covering stuff I'm interested for mblog currently. I should extend it as I go. The cases I've added reveal something I've noticed recently: The worst performing part of mime4cl seems to be the initial parsing of the message. My current theory is that this is due to the use of READ-LINE in DO-MULTIPART-PARTS which seems to ultimately dispatch to READ-CHAR internally due to the way our streams are set up. We should look into fixing this soon. It may be interesting to add this to windtunnel at some point, but I'd rather not burden a runner with this given that mime4cl is only worked on once every blue moon and I'm the only user. Change-Id: I001de3aac01f8aa7ea923b43b2db29cf66a4aac3 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12864 Reviewed-by: sterni <sternenseemann@systemli.org> Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
1 line
21 B
Text
1 line
21 B
Text
parent exposes tests
|