

shit tons of beers
Ummm…
I’m not sure my ass is up to a single 6-pack, much less tons of them.
I mean sure, lots of grease gives me runs like an Olympic sprinter, but this is a tall order.
shit tons of beers
Ummm…
I’m not sure my ass is up to a single 6-pack, much less tons of them.
I mean sure, lots of grease gives me runs like an Olympic sprinter, but this is a tall order.
Can you get mine while you are at it?
This echoes my thoughts… Even simple question/answer to help others get old games working, useful links to emulation resources for older platforms etc.
With steam deck popularity, a new wave of inexperienced folks wanting to try things is guaranteed.
I’ve had so many nights where I would have killed to be able to get into a sleeping position like this.
Curse this middle aged body of mine!
Executive order establishing the next deportations going to a new Martian “enrichment center” in 3… 2… 1…
Given their inclinations, I suspect alt-speak for slavery to be the next contestant on “What’s hot” on Xitter
Some parents are only good examples when under the category of “don’t do it like that”.
Looking forward to this
Good work! Love seeing a fellow seeder on here!
Da good stuff
lol I love how these always do the “We’ll get them all this time for sure!”
Awesome, so that’s good news. Disks probably just fine.
My next thoughts are on the service itself then… Your service providing the share might be getting throttled or not getting direct access to kernel hooks for performance.
Simplest test I would think is set up Samba or NFS in the host itself, not a container. Try a large transfer there. If speed isn’t an issue that way, then something at the container level is hindering you.
Hmm, at a glance those all look to be CMR.
To rule this out ideally, a tool like iostat (part of sysstat tools) can help. While moving data, and with the problem happening, if you run something like “iostat 1 -mx” and watch for a bit, you might be able to find an outlier or see evidence of if the drives are overloaded or of data is queueing up etc.
Notably watch the %util on the right side.
https://www.golinuxcloud.com/iostat-command-in-linux/ can help here a bit.
The %util is how busy the communication to the drive is… if maxed out, but the written per second is junk, then you may have a single bad disk. If many are doing it, you may have a design issue.
If %util doesn’t stay pegged, and you just see small bursts, then you know the disks are NOT the issue and can then focus on more complex diagnosis with networking etc.
What drives? If they are shingled, your performance will be terrible and the array runs a high risk of failing.
CMR is the way to go.
SMR behavior is about like what you describe… Fast until the drive cache is filled then plummets to nothing.
The story so far: In the beginning the Web was created. This has made a lot of people very angry and been widely regarded as a bad move.
Nice share. I had several of these little machines back in the day and it was cool to see this effort. Thanks!
Oh damn! Thank you!
Nice!
Unfortunately I don’t know the original creator.
Video without a summary or transcript?