Molecular0079

joined 1 year ago
[–] Molecular0079@lemmy.world 5 points 3 weeks ago

The failure to wait for network-online was the last thing preventing me from going rootless. I am going to have to try this again.

[–] Molecular0079@lemmy.world 2 points 3 months ago

Performance parity? Heck no, not until this bug with the GSP firmware is solved: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/538

[–] Molecular0079@lemmy.world 2 points 4 months ago

My issue with skins is that it is completely immersion breaking. You have Homelander and Gaia running around Call of Duty now. It's comical and just destroys my enjoyment of the game.

The skins get worse and worse because to continue the money machine they have to make more and more unique skins that just destroy the cohesion of the world they've built.

[–] Molecular0079@lemmy.world 13 points 4 months ago (6 children)

This. It all boils down to value for money. 5 dollars for a skin cosmetic is bullshit. 5 dollars or more for DLC with meaningful content is okay.

[–] Molecular0079@lemmy.world 3 points 5 months ago

Yeah, in a Reddit comment, Hector Martin himself said that the memory bandwidth on the Apple SIlicon GPU is so big that any potential performance problems due to TBDR vs IMR are basically insignificant.

...which is a funny fact because I had another Reddit user swear up and down that TBDR was a big problem and that's why Apple decided not to support Vulkan and instead is forcing everyone to go Metal.

[–] Molecular0079@lemmy.world 4 points 5 months ago (2 children)

I've heard something about Apple Silicon GPUs being tile-based and not immediate mode, which means the Vulkan API is different compared to regular PCs. How has this been addressed in the Vulkan driver?

[–] Molecular0079@lemmy.world 4 points 6 months ago

Huge fucking deal, especially for Nvidia users, but it is great for the entire ecosystem. Other OSes have had explicit sync for ages, so it is great for Linux to finally catch up in this regard.

[–] Molecular0079@lemmy.world 9 points 6 months ago

You're correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they're slower code paths.

The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.

I've tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.

[–] Molecular0079@lemmy.world 2 points 6 months ago (1 children)

Interesting solution! Thanks for the info. Seems like Nginx Proxy Manager doesn't support Proxy Protocol. Lmao, the world seems to be constantly pushing me towards Traefik all the time 🤣

[–] Molecular0079@lemmy.world 4 points 6 months ago (2 children)

I truly believe the answer to this question is going to be yes around the May - June timeframe when Nvidia releases their explicit sync enabled drivers. All aboard the Wayland hype train babyyyy!

[–] Molecular0079@lemmy.world 34 points 6 months ago (4 children)

I think there was some bad vibes when they got bought by a less than reputable company a while back. I know a lot of people, myself included switched to Mullvad. I am on Proton now though for the port forwarding.

[–] Molecular0079@lemmy.world 1 points 7 months ago (1 children)

I see. And the rest of your services are all exposed on localhost? Hmm, darn, it really looks like there's no way to use user-defined networks.

 

I've been trying to migrate my services over to rootless Podman containers for a while now and I keep running into weird issues that always make me go back to rootful. This past weekend I almost had it all working until I realized that my reverse proxy (Nginx Proxy Manager) wasn't passing the real source IP of client requests down to my other containers. This meant that all my containers were seeing requests coming solely from the IP address of the reverse proxy container, which breaks things like Nextcloud brute force protection, etc. It's apparently due to this Podman bug: https://github.com/containers/podman/issues/8193

This is the last step before I can finally switch to rootless, so it makes me wonder what all you self-hosters out there are doing with your rootless setups. I can't be the only one running into this issue right?

If anyone's curious, my setup consists of several docker-compose files, each handling a different service. Each service has its own dedicated Podman network, but only the proxy container connects to all of them to serve outside requests. This way each service is separated from each other and the only ingress from the outside is via the proxy container. I can also easily have duplicate instances of the same service without having to worry about port collisions, etc. Not being able to see real client IP really sucks in this situation.

view more: next ›