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

Latency issue grows by number of workers On Start, improve the cost of first query #34

Open
Opensourcecommunitydevelopment opened this issue Aug 1, 2017 · 0 comments

Comments

@Opensourcecommunitydevelopment
Copy link

Opensourcecommunitydevelopment commented Aug 1, 2017

improve the cost of first query
On Start the first query is slow because delay of worker Connection waiting created, so do it After init instantly and keepalive to be ready for querys.
Or workaround with a Pseudo query / HTTP2 WritePing To establish Connection directly After worker starts within the for worker Start loop!

Connection TLS Handshake RTT latencys

do Not Push query To worker that is Not ready!
may ping them every 5 minutes to verify they Are still alive and actually WORKING waiting for work (query.)

#35

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

No branches or pull requests

1 participant