Ah kay, definitely not a RAM size problem then.

iostat -x 5 Will print out per drive stats every 5 seconds. The first output is an average since boot. Check all of the drives have similar values while performing a write. Might be one drive is having problems and slows everything down, hopefully unlikely if they are brand new drives.

zpool iostat -w Will print out a latency histogram. Check if any have a lot above 1s and if it’s in the disk or sync queues. Here’s mine with 4 HDDs in z1 working fairly happily for comparison:

The init_on_alloc=0 kernel flag I mentioned below might still be worth trying.

deleted by creator

After some googling:

Some Linux distributions (at least Debian, Ubuntu) enable init_on_alloc option as security precaution by default. This option can help to prevent possible information leaks and make control-flow bugs that depend on uninitialized values more deterministic.

Unfortunately, it can lower ARC throughput considerably (see bug).

If you’re ready to cope with these security risks 6, you may disable it by setting init_on_alloc=0 in the GRUB kernel boot parameters.

I think it’s set to 1 on Raspberry Pi OS, you set it in /boot/cmdline.txtI think.

Exhaustive ZFS performance tuning guide

sync=disabled will make ZFS write to disk every 5 seconds instead of when software demands it, which maybe explains your LED behavior.

Jeff Geerling found that writes with Z1 was 74 MB/sec using the Radxa Penta SATA HAT with SSDs. Any HDD should be that fast, the SATA hat is likely the bottleneck.

Are you performing writes locally, or over smb?

Can try iostat or zpool iostat to monitor drive writes and latencies, might give a clue.

How much RAM does the Pi 5 have?

OpenAI noticed that Generative Pre-trained Transformers get better when you make them bigger. GPT-1 had 120 million parameters. GPT-2 bumped it up to 1.5 billion. GPT-3 grew to 175 billion. Now we have models with over 300 billion.

To run, every generated word requires doing math with every parameter, which nowadays is a massive amount of work, running on the most power hungry top of the line chips.

There are efforts to make smaller models that are still effective, but we are still in the range of 7-30 billion to get anything useful out of them.

You can read IAEA’s press releases for each attack. They go through the precise function and nature of each building and access the potential danger. Though they haven’t updated for the US’s latest bombing.

lol. Nicholas Kristof was in Beijing at the time, his contemporaneous article was critical of China and the CPC, but said “There is no massacre in Tiananmen Square, for example, although there is plenty of killing elsewhere.” The original article is paywalled, but here is a 2004 interview where he repeats that no one died in the square, and sticks to his death toll estimate of 300-800.

The Chinese Red Cross deny saying that, so I mean insert your own conspiracy for that one. No idea who the Swiss Ambassador was at the time, the reference is to a book.

The Clearing the Square section recounts the timeline of the military entering the square and it being totally empty by 6am. I guess you could count the three soldiers killed by the crowd, but that’s not what most people mean.

This is why I find this stuff so bewildering, even Wikipedia says no one died in the square. It was hectic around Mudixi, with buses of soldiers being torched and the burnted bodies being strung up. People there were absolutely shot at and killed.

It was an insane week with a lot happening, many different groups with their own motives, and so many details unclear. It’s weird that anti China rhetoric insists on something that didn’t happen, pushing a false narrative that’s so easy to dispell and distracts from the real violence and politics of the time.

My understanding is that it’s technically against their TOS but loosely enforced. They don’t specify precise limits since they probably change over time and region. Once you get noticed, they’ll block your traffic until you pay. Hence you can find people online that have been using it for years no problem, while other folks have been less lucky.

Basically their business strategy is to offer too-good-to-be-true free services that people start using and relying on, then charging once the bandwidth gets bigger.

It used to be worse, and all of cloudflare’s services were technically limited to HTML files, but selectively enforced. They’ve since changed and clarified their policy a bit. As far as I’ve ever heard, they don’t give a toss about the legality of your content, unless you’re a neo Nazi.

I’m guessing the cloudflared daemon isn’t connecting to jellyfin. You want to use http://. Also is jellyfin the hostname of the VM? Using localhost or 127.0.0.1 might be better ways to specify the same VM without relying on DNS for anything.

Personal opinion, but I wouldn’t bother with fail2ban, it’s a bit of effort to get it to work with cloudflare tunnel and easy to lock yourself out. Cloudflare’s own zero trust feature would be more secure and only need fiddling around cloudflare’s dashboard.