Stefan Seyfried wrote:
Am 03.03.2017 um 19:01 schrieb Carlos E. R.:
About the logs. You know that you can keep syslog standard logs, too. And even disable systemd writing logs.
No you can't. It will always put the journal in /run. And even with the journal on a ramdisk, it performs abysmally. (It takes more than 8 hours to read 4GB of journal (default size) from the ramdisk and output it to stdout, I'll see if I can find the bugzilla with all the dirty details, but since it's against SLES, it will probably be secret anyway).
--- 8 hours?! Even if it was compressed with "xz -9", it wouldn't take that long to decompress. Being on ram or disk shouldn't matter, since 4GB would fit in memory for many or most systems these days. Even if it was on a hard disk, the linux kernel, would, by default, buffer the file in memory if it was randomly accessed all over the place and used small I/O sizes. Even SSD's can be slow if you only do small I/O's. Sending a large email from Windows to my linux box -- when it stores it to the remote IMAP store, uses 4K packets. For a 24MB file, it took 225 seconds meaning I was getting ~110KB/s -- over a 10Gb link (SMB2 file read/write speed is about 200MB/s). Whereas on the IMAP server side, the disk BW is near 1GB/s and locally its coming off 4 SSD's in a RAID0 -- easily capable of over 200MB/s (near 600MB/s new). So disk I/O isn't the bottleneck it's the small I/O size that lowers BW by 2048! Also, possible slowing it down would be if it was decompression using direct-I/O rather than buffered I/O, or possible telling the kernel not to cache the journal under decompression -- so as to never get any benefit from the kernel's buffering. That just sounds too slow to be real -- i.e. you are talking about 146KB/s... and that's not even over a network. *suspicious* -- wondering about presence of delay loops to discourage people dumping logs... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org