We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Performance improvement needed.
I test 60K (350MB) json file, oboe, compare to browser native stream api is 10 times slower.
Only for small amount of data, difference is trivals.
Oboe, must have some over head over xhr.
If you use browser native stream api replace current xhr,
would it greatly improve the performance?
Now, for large data, I can't use oboe, it is way too slow. Instead, I just use browser native stream api , write simple parser on my own.
The text was updated successfully, but these errors were encountered:
I guess, not verified, the slowness of oboe, is caused by blob, Blob/FileReader , blob builder etc....
To make it fast, need to use var string = new TextDecoder(encoding).decode(uint8array);
var string = new TextDecoder(encoding).decode(uint8array);
there are several article talking about this slowness:
https://developers.google.com/web/updates/2012/06/How-to-convert-ArrayBuffer-to-and-from-String
https://stackoverflow.com/questions/6965107/converting-between-strings-and-arraybuffers
Sorry, something went wrong.
No branches or pull requests
Performance improvement needed.
I test 60K (350MB) json file, oboe, compare to browser native stream api
is 10 times slower.
Only for small amount of data, difference is trivals.
Oboe, must have some over head over xhr.
If you use browser native stream api replace current xhr,
would it greatly improve the performance?
Now, for large data, I can't use oboe, it is way too slow. Instead, I just use browser native stream api , write simple parser on my own.
The text was updated successfully, but these errors were encountered: