Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
Q: A faster re-implementaiton of jq written in Reason Native/OCaml
11–20 of 196 posts
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#12Are we sure it should get a single-letter 'q' binary name though? Docs seem to point that it's short for 'query-json'? Why not call it 'query-json' and let the user decide that as a shell alias or whatever. Even the ubiquitous 'ls' and 'cd' are two characters.
He replied and thought about qj
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#13Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#14Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
jq is pretty fast in my experience. But there have been cases where I've wanted it to be faster (dealing with a 90GB JSON file). The main weakness seems to be streaming use cases (not having the whole file in memory at once). These are supported, but the syntax is quite awkward.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#15I'd long for such a tool with a better comprehensible query language.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#16Are we sure it should get a single-letter 'q' binary name though? Docs seem to point that it's short for 'query-json'? Why not call it 'query-json' and let the user decide that as a shell alias or whatever. Even the ubiquitous 'ls' and 'cd' are two characters.
or at least qj
Happy to rename it to qj instead, but the option of renaming the binary it's a good workaround.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#17Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
jq is pretty fast in my experience. But there have been cases where I've wanted it to be faster (dealing with a 90GB JSON file). The main weakness seems to be streaming use cases (not having the whole file in memory at once). These are supported, but the syntax is quite awkward.
I should specify that on the performance section, Thanks!
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#18Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#19Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#20This looks nice, but I was a bit dismayed at "friends don't let friends curl | bash, to install this run curl | bash".
It wasn't.