On 03/04/2018 12:45 PM, Reinis Rozitis wrote:
That's what really kills performance, because of the async nature of
nginx. That's why I'm proposing an option to do the fsync at the end of
the PUT (or maybe even the whole operation) in a thread(pool).
Then again this way you make it again "asynchronous" (since it is/could be
waiting in some thread/pool (forever)).
Jesus, why? You start the fsync in a thread and you wait for it to be
completed with the HTTP response. Until this happens, the main thread
can service other requests.
Have you ever seen an async program which uses threads to run blocking
operations?
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
