Guten Tag Rhys Ulerich, am Mittwoch, 15. Januar 2014 um 16:11 schrieben Sie:
> Yeah. I was thinking that one would toss the file onto something > RAMish. But you're right that it won't have the performance profile > you want. Why would writing to a RAM-disk without buffering suffer performance? It may be slower than using memory mapped files with buffering, but the only problem coming into my mind would be filesystem overhead of the RAM-disk without buffering and that should be minimal because you don't change the file structure much but only call fsync pretty often. Depending on one's setup the persistant logging could be implemented outside the application by simply rsyncing the RAM-disk contents to a more persistent storage, which may even improve overall application performance because it doesn't need to log to two different targets anymore. I think it's worth measuring your approach. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
