On Fri, Nov 27, 2020 at 04:34:24PM +0100, Ronald Klop wrote: > >Mind to share these tips, so I can use them on my RPI4? ;-) sure! I'll write up a simple site later, but in summary this is what I've done subsequent to the initial setup. E&OE, if it breaks you get to keep both bits, no guarantees etc etc. In no particular order: 1. in /boot/msdos/config.txt there's this: over_voltage=6 arm_freq=2000 sdram_freq_min=3200 [I use a FLIRC case to keep it cool. you *must* use cooling for this. Max temps I'm seeing under very heavy compiling (it runs poudriere) is 72 degC in 25 degC ambient] 2. /usr/src /usr/ports /usr/local /usr/obj /home /var/cache/ccache are all on the usb3 disk, seperate datasets. 3. swap is 16GB and is the first partition on the usb3 disk 4. for compiling, ccache is a must. 5. set tmp to tmpfs in /etc/fstab. I use 1GB like this: tmpfs /tmp tmpfs rw,mode=1777,size=1024m 0 0 6. make things like mutt use this /tmp 7. enable powerd and on bootup. Make it almost always use the overclocked speed like this in /etc/rc.conf powerd_enable="YES" powerd_flags="-r 1" This makes it run _at_ 2GHz always without needing to set something like boost_turbo. 8. in /etc/sysctl.conf: vfs.read_max=128 # default 64 9. compile mutt with kyotocabinet which uses (I think) memory mapping for cache lookups things like that. Faster than on-disk. 10. Look up the spec of yr usb3 connected device. Does it have 4k sectors? If it does, if you're using zfs make sure vfs.zfs.min_auto_ashift=12 in /etc/sysctl.conf 11. if you do compile stuff it'd be worth using -j3 if you want reasonably responsive interactive use from the pi while it's compiling. Like I've said, this isn't even guaranteed to work. All I can say is it's whats working on my rpi4/8GB now and I'm very happy with it. -- J.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:26 UTC