-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-13 01:09, Anton Aylward wrote:
If and only if both a) you have this data on a separate file system from the 'system', and b) each file system can have its won cache then setting the cache(data) size to zero for the file system where you are storing the images will achieve what you want.
I don't think a zero (write) cache is appropriate either. He needs a cache in case the system is doing something else at the moment, so that it can delay the actual writing for some seconds. Normally the cache would be used all for this application, it writes so much. So being able to separate an appropriate cache for this application or this filesystem (whatever is feasible, if any) would be best. Say 2..4 GB for this, the rest for the system. Is this possible?
But if you can't use separate caches then shrinking the cache to zero will hurt other parts of the performance.
Right. And his real work system has more tasks to do.
I think being aggressive about page ageing and flushing aged pages is the best approach in that case.
Other tasks will be affected. Linda idea of using "posix_fadvise" and opening the file for write only seems to me a very good one. But she also said "the calls are advisory". - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG5SZoACgkQtTMYHG2NR9Uv3gCfdP+x15ukHQpOolZeN4GXl+LG qC4AniCajinllacGmRk4EaGYjzsdnpPj =MTpC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org