Live data from Hacker News

64 bit OS Raspberry Pi4 Benchmarks

medium.com

101–104 of 104 posts

Re: 64 bit OS Raspberry Pi4 Benchmarks

#101
post #39

Earlier quoted context omitted.

I'm running Firefox 73 on my BeagleBoard-X15 (Cortex-A15). Ubuntu 18.04. $ dpkg -l | grep firefox ii firefox 73.0.1+build1-0ubuntu0.18.04.1 armhf Safe and easy web browser from Mozilla

So that's why it's showing up with 59 being the latest versions from the distro for arm/arm64? https://packages.ubuntu.com/bionic/web/firefox

It's in bionic updates.

https://packages.ubuntu.com/bionic-updates/firefox

http://ports.ubuntu.com/pool/main/f/firefox/firefox_73.0.1+b...

Re: 64 bit OS Raspberry Pi4 Benchmarks

#102

One of the things that I find great about Raspbian is that the boot files are stored on a FAT32 partition which is readable from any OS, and there are some nice considerations for headless setups: drop in a wpa_supplicant.conf to configure Wi-Fi, `touch ssh` to get OpenSSH enabled at next boot. Do any of the alternative OSes, like Ubuntu, offer this?

Although there are some benefits, I see it as a complication.

The requirement of multiple partitions, with different filesystem types causes a lot of needless complication in the configuration and boot process.

Re: 64 bit OS Raspberry Pi4 Benchmarks

#103

One of the things that I find great about Raspbian is that the boot files are stored on a FAT32 partition which is readable from any OS, and there are some nice considerations for headless setups: drop in a wpa_supplicant.conf to configure Wi-Fi, `touch ssh` to get OpenSSH enabled at next boot. Do any of the alternative OSes, like Ubuntu, offer this?

The Ubuntu releases for the Raspberry Pi utilize cloud-init with the cloud-init configuration files being stored on the FAT32 partition.

Re: 64 bit OS Raspberry Pi4 Benchmarks

#104
post #35

Earlier quoted context omitted.

I wonder if using zram or zswap can help "eat" those overly long pointers in RAM via compression ?

I've never understood why zswap decompresses the pages before writing them out to disk. Disk IO is the slowest part of the whole chain, you've already paid to compress the data, why on earth would you throw that away AND use up more disk IO?

My guess is that this is due to some inherent limitations of the Linux kernel swap mechanism ? Possibly so that you can safely disable zswap at runtime (you can) ?

Or quite possibly no one implemented it just yet & writing uncompressed pages is transparently compatible with what normal swapping does.

Post reply on HN