Store intensively accessed cache files in /tmp instead of in nfs-mounted /home
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-meta (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Some applications like Google Earth, Povray and many many more store volatile but intensively accessed cache files in /home. When /home is NFS-mounted this causes for unnecessary network load and processing power which slows down the local network and the application.
When these applications are aware that their cache directory is in an NFS-mounted location, the could (or perhaps should) store their volatile but intensively accessed cache files in /tmp. (Of course with the proper accessing rights.)
This features should be implemented in the applications themselves. These will have to be identified first. Perhaps also the system has to have to information that it is desirable that in case /home is NSF-mounted, that these applications store their volatile but intensively accessed cache files in /tmp. Or the system can confirm that all should be in /home no matter if it is NFS-mounted of not.
Implementing this feature will allow for less network traffic, less processing power begin consumed which will result in higher user satisfaction and less wasting of energy.
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.