-
Notifications
You must be signed in to change notification settings - Fork 29
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
Performance comparsion with aiofiles #16
Comments
@daltonmatos the Linux aio.h implementation uses thread pool under the hood. You could read complete explanation here https://stackoverflow.com/a/8782305. The mosquito/aiofile has aio.h binding. And so it turns out that it works with internal system thread pool. On my tests, I don't see the performance increase. Moreover when the chunks are small this is slower than thread-pool implementation. IMHO: The one better thing is aio_fsync. It's a real do syncing file to the filesystem and on my experiments with raspberry pi after call aio_fsync a file was really stored on SD-card. By the way, I will be experimenting with libaio (not aio.h), but not yet. |
Thanks @mosquito for your response. @diogommartins, do you think this issue could be closed? Thanks. |
Thanks a lot, @mosquito ! |
I'm considering using aiofile for the FileHandler implementation of aiologger. Could you help me with the pros and cons comparing aiofile with aiofiles threadpool implementation ?
The text was updated successfully, but these errors were encountered: