Many places uox caches the mul data.
Looking at it, one may have a cleaner code if one mapped the files instead.
One could map the entire index files, and then map just a location of the data files (that becomes the "cache" so to speak.
Just a consideration.
Mapping versus caching
could be, yes.
Mapping does a few things:
1. Lets one share edits between process (so if one writes back, the other can get it)
2. The mapping to memory is handle by the OS. So depending on the size, it can be faster.
3. Cleanup can be nicer.
I recognize it won' make a big difference for UOX3 at this point. Other then perhaps cleaner code (and less), and perhaps faster startup. But it seemed like appropriate for discussion in this forum
Mapping does a few things:
1. Lets one share edits between process (so if one writes back, the other can get it)
2. The mapping to memory is handle by the OS. So depending on the size, it can be faster.
3. Cleanup can be nicer.
I recognize it won' make a big difference for UOX3 at this point. Other then perhaps cleaner code (and less), and perhaps faster startup. But it seemed like appropriate for discussion in this forum