Skip to content
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

Bad full sync performance #188

Open
yuuki0xff opened this issue Aug 19, 2019 · 0 comments
Open

Bad full sync performance #188

yuuki0xff opened this issue Aug 19, 2019 · 0 comments

Comments

@yuuki0xff
Copy link
Collaborator

NOTE: This issue will be fixed after #153 is fixed.

During the full syncing, nvpy sends many requests. But these sends one request at a time. The round trip time between Tokyo and Simplenote API server is about 140ms ~ 150ms. In this way, depending on the geographical location with the server, the time required for sync will increase.

To mitigate this effect, nvpy should support the multiple connections or websocket API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant