-
Notifications
You must be signed in to change notification settings - Fork 33
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
State the performance #43
Comments
And perhaps a comparison (performance & feature set) with jq? : https://github.com/stedolan/jq/ |
Thanks for the feedback! At the moment, I've never compared the performance against Regarding the feature set comparison, what would you expect? I don't have a deep knowledge of |
A little update: I still don't know which feature(s) should have benchmarks or not and where to put that (maybe a link to another doc like BENCHMARKS.md). For example, Given the following simple JSON nested arrays, let's say e.g. you want to flatten it (took the example from https://stedolan.github.io/jq/manual/#flatten,flatten(depth)): [1, [2], [[3]]] jqecho '[1, [2], [[3]]]' | jq 'flatten'
[
1,
2,
3
]
time bash -c 'for i in `seq 1 1000` ; do echo '"'"'[1, [2], [[3]]]'"'"' | jq 'flatten' > /dev/null ; done'
bash -c 24.85s user 0.86s system 100% cpu 25.451 total jqlecho '[1, [2], [[3]]]' | jql '...'
[
1,
2,
3
]
time bash -c 'for i in `seq 1 1000` ; do echo '"'"'[1, [2], [[3]]]'"'"' | jql '...' > /dev/null ; done'
bash -c 2.56s user 1.08s system 235% cpu 1.542 total |
I'll probably have a look at https://github.com/sharkdp/hyperfine and use it whenever I'll find some spare time. |
Some basic comparison benchmarks are now available here https://github.com/yamafaktory/jql/blob/master/PERFORMANCE.md (triggered every night). I'll try to add more of them. Closing for now. |
I suggest you to state whether jql is fast or not, and if the throughput is one of the goals of the project. As simple as it sounds, it may drive adoption.
Publishing benchmarks result may also help.
Good luck!
The text was updated successfully, but these errors were encountered: