Hi team,

I am new to memory mapped I/o concept. I am currently trying to implement memory mapped i/o so that my i/o intensive operations are fast.

Can anyone let me know how to implement this? Any suitable example link or steps will be helpful.

Thanks in advance.

I/O intensive operations ...

What is your use case? Is your process the only one or is concurrency an issue for your use case? If you can provide some more info about your application(s) you probably will get some good hints in this forum of what can be done better other than creating an own I/O concept. (I guess you are not the first and only person having thought about such work-to-do.)

Where I do not require persistence but speed in my use cases I try to make use of an in-memory database.

For my own write intensive use case in a single process I can say that SQLite3 is really fast in doing that job. I simply avoid any indexing and even the definition of a primary key - the only key I really rely on -when querying later on- is the ROWID to get the records out in original and correct sequence.

In others of my applications I try to do multiple inserts/updates within a single transaction, which has high impact on speed in my environment. Where avoidance of duplicates is required (because of key frame overlap) I use a primary key with the on conflict ignore clause.

Memory Mapped I/O does not increase I/O speed. The only wy to "speed up" I/O is to not do it at all. This has been the case for more than a century and is unlikely to change in the future unless the underlying limiting factor (called Physics) changes. Unfortunately, these underlying limiting factors have been stable and unchanging for BILLIONS of years and are unlikely to change in your lifetime.

Memory-mapped I/O merely eliminates a buffer copy operation and might also eliminate a transition between user and supervisor mode.