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

Accelerated I/O via memory mapped files #118

Open
byeongkeunahn opened this issue Dec 25, 2024 · 0 comments
Open

Accelerated I/O via memory mapped files #118

byeongkeunahn opened this issue Dec 25, 2024 · 0 comments

Comments

@byeongkeunahn
Copy link
Collaborator

Currently, standard I/O implementation uses buffers internally. Although this achieves a good performance, it falls short of I/O via memory mapped files due to the copy occurring twice. Hence, it may be desirable to use I/O via memory mapped files for maximal performance. However, multiple scenarios must be handled properly to guarantee robustness. For example, I/O via memory mapped files won't work with pipe streams connected to a console. The implementation thus must detect whether I/O streams are pipes or redirected to files at runtime and enable I/O via memory mapped files only in the latter case. Also, care must be taken to minimize code duplication for handling both scenarios.

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