-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add test and improve performance #4
base: master
Are you sure you want to change the base?
Conversation
package.json
Outdated
"standard": "^11.0.1" | ||
"budo": "^11.6.3", | ||
"puppeteer": "^3.0.2", | ||
"random-access-test": "github:random-access-storage/random-access-test", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i didn't realise we had this! should we publish that to npm?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed the same. We should, I think is really helpful to test these modules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
published
These changes looks great @tinchoz49. Anything I can do to move this forward? |
Hey @arj03 thanks :). We are testing this PR in our application and trying to get stability. It seems working but we are having a race condition issue and we need to check if it belongs to this PR or not. After that I will put into review next week. |
Been testing this, not sure about the speed diff, but at least I didn't get any errors from manual testing with this new code. |
0bd3705
to
816729f
Compare
816729f
to
7c73c6f
Compare
On further testing I'm getting a few of these: Could not satisfy length |
The recently support for chrome 81 decrease the performance since we have to get on every read/write an updated
entry.file
: #3This PR improve that:
The
write
process only use thesize
prop of the file, something that we can get updated on every write request and just use that information instead of getting a new entry file.The
read
process is different, it needs the updated file, so every time that we write into the file wemarked to update
. With this approach only when the file was really updated it would try to get a new entry file.current version
PR version