http://bugzilla.suse.com/show_bug.cgi?id=911347 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(bpesavento@infini | |to.it) --- Comment #22 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Bruno Pesavento from comment #21)
Created attachment 621355 [details] Flushing times with /var/log mounted with autodefrag option
Mounting /var/log autodefrag is definitely a better workaround: flushing time is still less than 4 s with a 41.9 MB system journal. Now removed the 34MB limit, to be able to test upcoming patches with larger files.
Ok, thanks for the feedback. We might still set an upper limit for the journal files, because the manpage states: -->-- autodefrag Disable/enable auto defragmentation. Auto defragmentation detects small random writes into files and queue them up for the defrag process. Works best for small files; Not well suited for large database workloads. --<-- But this rather refers to files of gigabyte size. Can you test with SystemMaxFileSize up to 1Gb and check wheter you see any negative impact? -- You are receiving this mail because: You are on the CC list for the bug.