Selfhosted

40347 readers

330 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

112

How responsive is your Nextcloud? (sh.itjust.works)

submitted 8 months ago* (last edited 8 months ago) by Kalcifer@sh.itjust.works to c/selfhosted@lemmy.world

75 comments fedilink hide all child comments

My Nextcloud has always been sluggish — navigating and interacting isn't snappy/responsive, changing between apps is very slow, loading tasks is horrible, etc. I'm curious what the experience is like for other people. I'd also be curious to know how you have your Nextcloud set up (install method, server hardware, any other relevent special configs, etc.). Mine is essentially just a default install of Nextcloud Snap.

Edit (2024-03-03T09:00Z): I should clarify that I am specifically talking about the web interface and not general file sync capabilites. Specifically, I notice the sluggishness the most when interacting with the calendar, and tasks.

you are viewing a single comment's thread
view the rest of the comments

[–] LufyCZ@lemmy.world 7 points 8 months ago (9 children)

Not in this context. Bare metal means all packages and services installed and running directly on the host, not through docker/lxc/vms

[–] atzanteol@sh.itjust.works -1 points 8 months ago* (last edited 8 months ago) (8 children)

Yes - in this context containers run on bare metal. They run directly on the host. They even show up in the host's process list with PIDs. There is no virtual machine between an executable running in a docker image and the CPU on the host.

[–] LufyCZ@lemmy.world 4 points 8 months ago (7 children)

Have you read my comment? It's about where the packages and services are installed.

In this case, they're installed in the container, not on the host

[–] teawrecks@sopuli.xyz 5 points 8 months ago

It's all about where the packages and services are installed

No. Your packages and services could be on a network share on the other side of the world, but where they are run is what matters here. Processes are always loaded into, and run from main memory.

"Running on bare metal" refers to whether the CPU the process is being run on is emulated/virtualized (ex. via Intel VT-x) or not.

A VM uses virtualization to run an OS, and the processes are running within that OS, thus neither is running on bare metal. But the purpose of containers is to run them wherever your host OS is running. So if your host is on bare metal, then the container is too. You are not emulating or virtualizing any hardware.

Here's an article explaining the difference in more detail if needed.

load more comments (6 replies)