1
18
matthewc

@lemmy.self-host.site

matthewc 90 points 3 years ago

macOS

path: 0 957873, hotness: undefined, score: 90, children: 0
matthewc 13 points 3 years ago

Yet the same people still expect meteorologists to use the same science to predict the weather for them.

path: 0 1019869 1021074, hotness: undefined, score: 13, children: 1
matthewc 11 points 3 years ago

Exactly what you said. It has always been about control.

path: 0 2325871 2327472, hotness: undefined, score: 11, children: 0
matthewc 10 points 3 years ago path: 0 1020556 1037155 1041123, hotness: undefined, score: 10, children: 0
matthewc 7 points 3 years ago

Developer here. Completely depends on your workflow.

I went base model and the only thing I regret is not getting more RAM.

Speeds have been phenomenal when there binaries are native. Speeds have been good when the binaries are running through Rosetta.

The specs you’re wavering between are extremely workflow specific. You know if your workflow requires the 16 extra GPU cores. You know if your workflow requires another 64 GB of RAM.

path: 0 2124049, hotness: undefined, score: 7, children: 4
matthewc 5 points 3 years ago

So far so good on my little one user instance as well.

path: 0 957775 957838, hotness: undefined, score: 5, children: 0
matthewc 4 points 3 years ago

I’m running on my NAS.

path: 0 957775 957850 958272 958883 976451, hotness: undefined, score: 4, children: 2
matthewc 4 points 3 years ago

Raising the standard enables new uses of technology.

path: 0 1723066 1733400 1734927, hotness: undefined, score: 4, children: 2
matthewc 3 points 3 years ago

Serious. I installed VSCodium today.

path: 0 1292407 1293605 1306116 1310456, hotness: undefined, score: 3, children: 0
matthewc 3 points 3 years ago

Use two providers on different networks. They can fill in the gaps for each other.

path: 0 1141953 1142127 1160016, hotness: undefined, score: 3, children: 1
matthewc 3 points 3 years ago

I spin up a lot of Docker containers with large data sets locally.

path: 0 2124049 2145372 2147359, hotness: undefined, score: 3, children: 0
matthewc 2 points 3 years ago

I highly recommend storing your DB and pictrs directories on an SSD volume.

path: 0 957775 957850 958272 958883 976451 981140 981323, hotness: undefined, score: 2, children: 0
matthewc 2 points 3 years ago

I added 16GB to mine. It was recognized without me doing anything special. I run about 15 Docker containers in addition to the normal Synology suite. I only end up using about 3 GB of ram, but I don’t mind having 17 GB available for paging.

path: 0 1048963, hotness: undefined, score: 2, children: 1
matthewc 2 points 3 years ago

Not just performance; I can’t imagine it would be good for five drives of a volume to go missing if a single cable fails.

I’m wondering if I can move my four current drives into the DX517 and save the volume. Can I just move the drives around without consequence?

I’m starting to think a second NAS full of SSDs would be best to host home lab applications off of instead of trying to make it work with my current NAS and an expansion unit.

path: 0 1050211 1050398, hotness: undefined, score: 2, children: 1
matthewc 2 points 3 years ago path: 0 1290377 1292601 1327967 1332918 1352516, hotness: undefined, score: 2, children: 4
matthewc 1 point 3 years ago

In my experience restart are infrequent. DSM runs plenty fast.

When I have a container that performs frequent small read/writes, i.e. lemmy and pictrs, I put those directories on a USB connected SSD. That greatly increased the performance of the containers I moved to that solution.

My other biggest performance boost was caching my main volume with two NVME SSDs.

path: 0 1290377 1292601 1327967 1332918 1352516 1363125 1371763 1373707 1374421, hotness: undefined, score: 1, children: 0
matthewc 1 point 3 years ago

I didn’t realize vscode is open source. Good to know!

path: 0 1292407 1293605, hotness: undefined, score: 1, children: 2
matthewc 1 point 3 years ago

You’re welcome.

I’m not sure if you’ll get a speed benefit or not since there is no way to prioritize the SSD.

path: 0 1290377 1292601 1327967 1332918 1352516 1363125 1371763, hotness: undefined, score: 1, children: 2

thanks for using Leebra!

go to feed...