| ▲ | jclarkcom 6 days ago |
| You might look into using memory mapped IO for reading input and writing your output files. This can save some memory allocations and file read and write times. I did this with a project where I got more than 10x speed up. For many cases file IO is going to be your bottleneck. |
|
| ▲ | Sesse__ 6 days ago | parent [-] |
| mmap-based I/O still needs to go through the kernel, including memory allocation (in the page cache) and all. If you've got 10x speedup from mmap, it is usually because your explicit I/O was very inefficient; there are situations where mmap is useful, but it's rarely a high-performance strategy, as it's really hard for it to guess what your intended I/O patterns are just from the page faults it's seeing. |
| |
| ▲ | jclarkcom 5 days ago | parent [-] | | Windows uses memory mapped IO for loading all executable processes because it allows you to start executing a process after loading a few pages even if the exe is megabytes. You can use the same to reduce latency for starting to assemble data before the rest of the file loads, the rest can be loaded using more efficienct asynchronous mechanisms. Using for output also means your process doesnt waits on flushes that is also async. And in memory constrained environments the OS doesn’t have to write your data to swap, it can just reload it from the meeting mapped file. | | |
| ▲ | Sesse__ 5 days ago | parent [-] | | Linux also uses mmap for running executables. But explicit I/O does not mean you have to start off by a gigabyte-long read(). | | |
|
|
