-
Notifications
You must be signed in to change notification settings - Fork 978
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
nodejs or/and webassembly binary ? #44
Comments
Yes. WebAssembly is probably out for the time being, but a native node extension is something that ought to be done. |
Say we have a working Node binding to simdjson. In the readme, it reads:
Does this mean that, this library would not be a suitable replacement for |
The issue is not resolved yet, why close then ? |
If you are parsing a single line of JSON, then it is unlikely that the time spent parsing is significant enough to warrant optimization unless you are parsing many, many such cases. And at that point, things like function call overhead and memory allocations are likely to dominate your running time. This is potentially interesting, but it is not something that this library was optimized for. |
In what size of json file we can expect the benefit? if that is known, I think it will switch in using this instead? but for me, as it is working best as a compiled binary..maybe a node script that Interface it using child_process is more suitable? |
const [isOnline, setIsOnline] = add(users, isOnline(friend.id)); |
From the README: "Performance is optimized for JSON documents spanning at least a tens kilobytes up to many megabytes". This library (simdjson) is for processing large volumes of JSON. |
My statement above were deliberately pessimistic: simdjson does very well even on tiny documents. At the time I wrote the above comments, I had not benchmarked simdjson on tiny documents. |
Is it plan to export as nodejs or/and webassembly binary ?
The text was updated successfully, but these errors were encountered: