chipmunk
chipmunk copied to clipboard
Rust session: mapping file on linux
Mapping of files with size > 1 Gb takes very different times on different platforms. For example 1,8 Gb text file:
- macos 1-2 sec
- linux - ~10-15 sec
- windows - no measurements yet
From the user perspective (UI) it looks like during this time (mapping file time) nothing is happen. Suggestions:
- confirm the issue with linux on a virtual machine to exclude specific OS case (my tests were done with Arch Linux)
- optimize text file mapping for linux
- modify mapping: split process into segments. Like read the first 100 Mb - report; the next 100Mb - report and so on. It will allow keeping UI updated.
Sorry, I've used (again) wrong harddrive. On my linux SDD it takes ~2 s. Well performance is in borders of normal. But as for hdd drivers... shell we think about updating state during mapping of file?
Related to #1993