deadbeef

Yep, any time you have a traffic cap or bill for traffic you've got to have data to back up what you are billing for.

More recently CDN's ( and widespread SSL adoption ) have made it a whole lot less obvious what sites the user is going to. I suspect that nice clearcut list of porn sites from 2007 would just look like some cloudflare, akamai and google these days.

There's no way of knowing what happened there.

But back in the mid to late 2000's we had a whole bunch of residential internet customers and every so often one would blow their traffic cap by a bunch and would ring up and say "Your billing system is wrong!".

Then whoever could be bothered in the office would do some modest analysis on their netflow data and come up with something like "18% of your traffic this month was redtube.com, 33% was pornhub.com and 9% was xhamster.com.

We never knew if whoever was on the phone was the raging porn addict or it was one of their associates. Either way they would say "Oh well, I guess we will never know then. Thanks for your help. Bye.". Followed by them quietly paying the bill.

Haha, 144p @ 60hz is fricking hilarious.

Reminds me of seeing completely rubbish resolution real player videos embedded in websites back in the late 90s and me thinking, "Well that isn't ever going to take off".

I just read the update to the post saying that the issue has been narrowed down to the NTFS driver. I haven't used NTFS on linux since the NTFS fuse driver was brand new and still wonky as hell something like 15 years ago, so I don't know much about it.

However, it sounds like the in kernel driver was still pretty fresh in 5.15, so doing as you have suggested and trying out a 6.5 kernel instead is a pretty good call.

If you haven't already, try running hdparm on your drive to get an idea of if the drives are at least doing large raw reads straight off the disk at an appropriate performance level.

This is output from the little NUC I'm using right now:

# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 465.8G  0 disk 
├─sda1   8:1    0   512M  0 part /boot/efi
├─sda2   8:2    0 464.3G  0 part /
└─sda3   8:3    0   976M  0 part [SWAP]

# hdparm -i /dev/sda

/dev/sda:

 Model=Samsung SSD 860 EVO 500GB, FwRev=RVT02B6Q, SerialNo=S3YANB0KB24583B
...

# hdparm -t /dev/sda

/dev/sda:
 Timing buffered disk reads: 1526 MB in  3.00 seconds = 508.21 MB/sec

If your results are really poor for this test then it points more at the drive / cable / controller / linux controller driver.

If the results are okay, then the issue is probably something more like a logical partitioning / filesystem driver issue.

I'm not sure what a good benchmark application for Linux that tests the filesystem layer as well is other than bonnie++ which has been around forever. Someone else might have a more current idea of something to use for this.

It might help for the folks here to know which brand and model of SSDs you have, what sort of sata controllers the sata ones are plugged into and what sort of cpu and motherboard the nvme one is connected to.

What I can say is Ubuntu 22.04 doesn't have some mystery problem with SSDs. I work in a place where we have in the order of 100 Ubuntu 22.04 installs running with SSDs, all either older intel ones or newer samsung ones. They go great.

1988 Nissan Skyline GT with an RB20DET.

It was abandoned by my uncle at our place when he moved overseas and subsequently my sister drove it around a bit. Eventually it leaked coolant from the water pump, overheated and blew a head gasket because she wasn't paying attention.

I was unemployed and bored and I decided to pull it apart and bought all the bits to fix it. I didn't really know anything about mechanical stuff at the time, but I am good at logic and try not to be useless at practical stuff even though I'm really a computer geek. I drove it around for a bunch of years after that until I was earning enough money that I could buy something I wanted which was a Mitsubshi EVO 1.

So to answer the question, favorite thing was that I rescued it from oblivion even though I didn't know much about cars or engines at the time.

The situation is mostly reversed on Linux. Nvidia has fewer features, more bugs and stuff that plain won't work at all. Even onboard intel graphics is going to be less buggy than a pretty expensive Nvidia card.

I mention that because language model work is pretty niche and so is Linux ( maybe similar sized niches? ).

Please drink a verification can to continue.

The samsung TV that I bought for my son had this annoying overlay thing that pops up when you turn it on that shows all the different inputs and nags about various things it thinks are wrong with the world. It is plugged into an Nvidia shield that we do most things on, but you can't use the shield until the overlay calms the fuck down and disappears.

It'd be great if you could just have the thing turn on and display an input like our older TVs do.

This damnable prison of log and ice eats away at my fibre. I find the lack of culture astonishing.

Agreed, it seems like they should have put just a little bit more in the standard feature set so every little window manager doesn't have to reinvent the wheel.