-
Notifications
You must be signed in to change notification settings - Fork 31
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
implement a connection pool #75
Conversation
290ccd5
to
043e0e8
Compare
Any updates on this PR? |
@thangngoc89 I think I'd be more comfortable if someone else reviewed my code. If @whilefalse has idea on how to actually make the |
@c-cube I see. I will blindly use this branch and hope for the best 🤞 |
Hey. I can certainly have a look, I’m not really an OCaml expert but if it’s related to my changes I’ll happily have a look. Do you have any more information on what the problem with the ports is? I’ll try to have a look tomorrow when I’m back at my computer but any info you have would help. |
@whilefalse awesome! take your time, it's just that I rebased the thing and had some tricky merges for the test suite. My question is more: can we make the |
.github/workflows/main.yml
Outdated
@@ -4,6 +4,7 @@ on: | |||
push: | |||
branches: | |||
- master | |||
- wip-pool |
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.
This was part of draft PR (i don't think you want to merge this)
The build issue are unrelated to windows but more to setup-ocaml. On my repo setup-ocaml doesn't manage to setup certificate, in this PR it can't restore cache. I tried to build with esy (it sandbox more than opam) and it builded. I try
Seem like missing deps. esy pulled OCaml 4.13 |
I guess the opam files need:
|
Seems like there was some action on this PR as of Jan 7, 2022. Are there any updates? Has this task been accomplished by another PR? |
Not particularly, it's just that right now it needs some actual testing. If you're interested in the feature you could use |
see #44 for the use case. It also makes benchmark faster (e.g. a parallel merge sort of a list of 3000 elements on top of redis, which stresses latency a lot, goes from 15.2s to 11.2s using a pool of 32 connections on the local network interface).
To run the merge sort bench: