Hi all,
I use the steefdebruijn/docker-roonserver image to run on my nas (btw: thanks steef for the effort).
My nas has /tmp mapped to memory (tmpfs).
I now have mounted this /tmp to the /tmp in the container and I get the idea it is faster in response.
Anyone else doing this and does it makes sense anyway?
(While it does not do any harm I guess, I rather remove it from the config to not overcomplicate stuff when objectively useless.)
Curious to find if others experience a difference or can debunk this ideaā¦
(must admit that the only roon related stuff in /tmp seems to be the lock and some dotnet diagnostic debug sockets, so little evidence for use of the /tmp folder?)
So ātmpfsā is a memory backed file system, hence the speed. Thereās no issue with mapping the docker image ā/tmpā there bar the possibility of file name clashes with the NAS host. You could use a subdir on ā/tmpā or a dedicated ātmpfsā to avoid this. Do be aware that all of this is using a portion of the NAS RAM. This can be size limited or left unbound. If bounded there may be limited space which you fill. If unbounded then it may start to fill the RAM space. If memory serves ātmpfsā is amongst the first things chosen for disk paging, so not too bad. Relying on applications unknown ātmpā behaviour will bite you someday. Iāve heard and spoken the āitās never done that beforeā words many times.
In theory, there should be no issue mapping /tmp to /tmpfs because neither are intended to persist across reboots (/tmp because of semantics, /tmpfs because of volatility). Is doing this mapping within your Roon container actually going to improve anything materially? Probably not. Is it going to cause problems? Probably not. Would I do? Probably not.
