-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad tagsoup performance #83
Comments
(the real profile is 44MB, and github won't let me upload it, so that's having trimmed out all of the non tagsoup/pandoc stuff) |
I'd describe the state as somewhat dormant. I started a rewrite that vastly improves performance, but only got halfway through, so there's nothing usable there. If you send a patch I'll apply it, but I don't really have the cycles to do any investigation/optimisation myself. I no longer really use the library. I'd welcome handing over maintainership if anyone stepped up. |
Darn. I suspected that was the case :( |
I have a similar experience using scalpel that internally uses TagSoup: @ndmitchell which steps would be required to bring TagSoup major performance improvements? |
https://github.com/vshabanov/fast-tagsoup is an in-place replacement for |
That fast-tagsoup project looks either dead or complete. Or would you recommend to copy the code over an maintain it here? |
Hi all,
I'm writing some quickcheck tests against arbitrary
Text.Pandoc.Block
s that print and then reparse theBlock
s. The test runs 100 times, and usually burns out 8+GB of RAM. Attached is the-p
, which as you can see, is dominated by tagsoup:I'm not sure what the state of this project is, but I'd be happy to provide a repro.
The text was updated successfully, but these errors were encountered: