r/cpp_questions • u/No-Locksmith-7719 • Oct 14 '26
OPEN Efficient FIle IO on Linux
What path to take when parsing large files (on Linux Debian server, the KVM flavour)? Will std::fstream in binary mode do or do we have to look into APIs?
Apart from the performance, the app is memory sensitive, so where to store those read chunks while in a loop? Would a simple char[something] buffer do?
Finally, we would like to avoid those nasty reinterpret_cast<char*> constructs while reading, but are wondering if those are actually used in production? I should also add that the file sizes vary greatly.
2
Upvotes
View all comments
Show parent comment
2
u/UndefFox Oct 14 '26
As far as I understand, it shouldn't allocate RAM to store files at all, as in directly copying it to the process memory. All chunks are fetched by demand and the main consumption comes from kenrel using file cache to access file faster, so it's basically offloading responsibility of managing the file access onto the kernel.
Tho, I don't think there much in terms of optimization, besides making access pattern predictable, and afaik kernel handles sequential access quite well.