# JSON Library Benchmarks

**URL:** <https://forum.elixirforum.com/t/json-library-benchmarks/23076>\
**Category:** Discussions\
**Tags:** benchmark, discussion, json\
**Created:** [June 11, 2019, 3:15pm UTC](https://forum.elixirforum.com/t/json-library-benchmarks/23076 "2019-06-11T15:15:28Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![sunny-g](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/sunny-g/32/6826_2.png) [@sunny-g](https://forum.elixirforum.com/u/sunny-g)\
**Post date:** [June 13, 2019, 2:56pm UTC](https://forum.elixirforum.com/t/json-library-benchmarks/23076/23 "2019-06-13T14:56:13Z")

</div>

I believe I am using the dirty scheduler for [these](https://github.com/sunny-g/serde_rustler/blob/master/serde_rustler_tests/native/serde_rustler_tests/src/lib.rs#L22) functions, which I believe is why they run faster on larger inputs (Issue 90 and GovTrack), but I think I see your point - `jiffy` might be/is “pre-emptively” handling yielding (rather than what my first approach would be, which is to switch between the two functions depending on the size/complexity of the input).

And thats good to know about the `parallel` option, I ought to add to/replace the existing benchmarks with non-parallel versions and publish the results. Thanks!

---

_[View the full topic](https://forum.elixirforum.com/t/json-library-benchmarks/23076)._