Store intensively accessed cache files in /tmp instead of in nfs-mounted /home

Bug #132459 reported by Pander on 2007-08-14
Affects Status Importance Assigned to Milestone
ubuntu-meta (Ubuntu)

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.

Brian Murray (brian-murray) wrote :

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.

Pander (pander) wrote :

As a quick fix I manually created some links so that these cache directories with intensive read and write actions was not on my NFS mounted home directory. so if nothing has been done this problem still exists. For users that have an NFS mounted home and which are not expert users, you can expect that they will be very unsatisfied with applications that behave like described before. In order to have them experience all the applications offered by Ubuntu in a pleasant way, it might be good for Ubuntu package guidelines to create/move these kind of cache dirs to /tmp and notify the user about it. Implementing a guideline of this kind for all packages would definitely ensure much greater user satisfaction.

Bryan Quigley (bryanquigley) wrote :

Thanks for taking the time to report this and help make Ubuntu better. Unfortunately you would need to report bugs to each of those projects individually to have this fixed.

In present systems swithing them to use /run might be best -

Changed in ubuntu-meta (Ubuntu):
status: Confirmed → Invalid
Pander (pander) wrote :

Could you propose this as a guideline or possible risk that all packagers should look at when packaging?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers