Hi, Le samedi 10 novembre 2007 à 15:58 +0100, Miro Dietiker a écrit : > I followed this discussion and finally thought about what are we using > tmpfiles for... > I see some typical applications where huge tmp comes into place: > Say i'm processing huge amount of data (but i'm not using a > database-like thing). > Sometimes it makes sense to place chunks of huge files into tmp - such > as expanded images, parts of a huge pdf build, ... > > There are apps use tmp in this way to get rid if memory usage for things > which need e.g. no continous permanent random access - say few writes, > few reads (in my case: one write, one read). > This generally is associated with the intention to have RAM and swap > untouched, unpolluted and system resources perform as none such > resources where used. > > I'm processing this way huge amount of data (Gigabyte PDFs with image > data) and never associated using /tmp to relate memory or swap usage. My > memory and swap would not be enough to do so... I have not tested such uses, especially those involving so large files, but I don't think you would see much difference if you just replaced your 2 GB /tmp partition by a tmpfs and 2 extra gigabytes of swap. In all cases, I'm not sure /tmp is the best filesystem for handling manipulation of such large data; at least, I would not rely on it on all computers. Especially those where /tmp is on the root filesystem. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=