Comment # 23 on bug 911347 from Bruno Pesavento

(In reply to Thomas Blume from comment #22)
> (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?

I'll let the file grow unconstrained (unless I hit a wall...), but think the
default max is 128MiB (see comment #7).