Idea:
The new ic-polyfill function mounts some virtual memory in the file system. Whenever a user tries to read or write in this file, the read and write operations work directly on the virtual memory as if it was one of the files on the filesystem. Direct memory access is much faster because there is less inherent data copying, and no extra overhead related to the use of complex data structures such as btreemap. This creates a "fast file" at the cost of using one dedicated virtual memory storages. The user can mount several virtual memories, however, the number of virtual memories is limited.
The feature can have several purposes:
Fast file for reading and writing can be helpful for applications like sqlite or some application related to intensive reading and writing to some particular file.
A user can see their own virtual memory from the perspective of the file system or the wasi file system calls.
Comparison with the fast file can be a sort of a baseline for estimating performance of work with the usual files.
Idea: The new ic-polyfill function mounts some virtual memory in the file system. Whenever a user tries to read or write in this file, the read and write operations work directly on the virtual memory as if it was one of the files on the filesystem. Direct memory access is much faster because there is less inherent data copying, and no extra overhead related to the use of complex data structures such as btreemap. This creates a "fast file" at the cost of using one dedicated virtual memory storages. The user can mount several virtual memories, however, the number of virtual memories is limited.
The feature can have several purposes: