-
Notifications
You must be signed in to change notification settings - Fork 48
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 function read_blocking/write_blocking and alike (fixes also a dep… #101
Conversation
My latest commit fixes #102 : a bug in Ssl.flush with non blocking socket. |
I did some timing. On medium size (50Mb) size transfer, no releasing the lock is new to a factor 2 gain, because it saves releasing the lock. On simple_httpd, using domains, we go from |
Sorry, but I am about to release simple_httpd. I do not want to fork ocaml-ssl (I think this is rude and bad for the comunity). In the meantime, I add ocaml-ssl with this PR and version updated to 0.6 as a sub module. If we converge to an accepted PR, I will remove this submodule. |
…recation in a tests). This function are grouped in two module: Release with the original behavious and the new ones in NoRelease
I used rebase to cleanup the commit list for easier review. |
This PR looks fine to me on principle and first pass and, if the performances you mention are real, would be warranted. We passed control of this module over to @anmonteiro and co. so I believe it would be up to them to accept the patch if they want to. Consider this as my emeritus maintainer approval |
This PR has seemingly grown in scope since it was first opened. @craff would you mind reverting the opam file change, and submitting the deprecations in a separate PR? |
Antonio Nuno Monteiro writes:
This PR has seemingly grown in scope since it was first opened.
@craff would you mind reverting the opam file change, and submitting the deprecations in a separate PR?
Done: PR 106 and PR 107 (for deprecation). PR107 is base on PR106, there
was conflict to rebase on master and I think it is ok like that, I will
rebase PR107 on PR106 to follow change asker by reviewver.
There is a build error or a deprecated warning in a test related to
Thread.Exit. One should decide if we keep the warning or if we ignore
older ocaml version ?
Cheers,
Christophe
…--
Christophe Raffalli
tél: +689 87 23 11 48
web: http://raffalli.eu
Ce mail est signé avec pgp (Pièce jointe signature.asc, clef sur https://raffalli.eu/pgp)
This mail is signed pgp (Attachment signature.asc, clef on https://raffalli.eu/pgp)
|
I close this PR as it is replaced by the two others. |
I wanted to test with these as my project Simple_httpd uses non blocking sockets. I observed a 2-3% amelioration in very stressing condition (100 downloads simultaneous, using only 6 domains/cores)
So it may be worth a PR?
(fixes also a deprecation in a tests)
If you wish to accept this PR, I will add the necessary tests.