4 ms·

“Deploy a hobby instance in one line on Linux with Docker (recommended 16 CPU cores, 32GB RAM, 256GB disk” Cant say I would call these specs “hobby” at all

JimmyAustin 3y ago
Just about anything with only one instance is essentially hobby.
- mrits 3y ago
  Hard disagree. A hobby instance should be able to be spun up in the cloud on a free or near free tier.
- KronisLV 3y ago
  > Just about anything with only one instance is essentially hobby. Not high availability? Sure. However, I've seen software out there that ran as a monolith with a single deployment unit, facilitated lots of business processes and entire teams of people for continued development. Not everything necessarily needs high uptime, either. Some software can also serve particular time zones and have ample windows for scheduled maintenance, upgrades and so on. There's probably at least a few classifications between hobby projects on one end and HA distributed systems on the other. >> Cant say I would call these specs “hobby” at all With this, however, I'm inclined to agree. In my eyes, "hobby" would imply something more along the lines of: "Just give this half a CPU core and about 512 MB of RAM, maybe up to a GB of storage depending on what you'll use it for, it'll probably work well enough for a few users." Some software that mostly fits that definition, in my experience: Nextcloud, Apache2/Nginx/Caddy, Grav, Mattermost, Gitea, Heimdall, YOURLS, PrivateBin, phpBB, Uptime Kuma, Zabbix, PostgreSQL, MySQL/MariaDB, Redis, RabbitMQ, Docker Swarm and plenty others. Some software that needs more resources: SonarQube, PeerTube (for encoding), OpenProject (Ruby app), Sonatype Nexus (bloated Java app, but lots of functionality), Matomo (issues with displaying historic data with low resources), BackupPC (compresson of backups), K3s and other Kubernetes cluster distros and plenty others, too. Not to say that it somehow makes the software worse, just that people have different expectations. Perhaps more realistic expectations on my part for hobby software should be: "You should be able to launch it with whatever spare resources your laptop has."
deleted 3y ago
[deleted]
vadman97 3y ago
Apologies for the inconsistency here. Our Docker resource requirement recommendations were out of date after some recent improvements (https://github.com/highlight/highlight/pull/5074 https://github.com/highlight/highlight/pull/5074 and https://github.com/highlight/highlight/pull/4993 https://github.com/highlight/highlight/pull/4993). Just updated this: 8GB of RAM, 4 CPUs, and 64 GB of disk space.
- that_guy_iain 3y ago
  8GB of ram? For a hobby? Very resource intensive, eh?
  - redskyluan 3y ago
    Totally agree with that. 8G might be too much to make the open source product popular. I would say 4G may more sense to me, I know how much engineering effort it requires though. LOL
    - wvh 3y ago
      Unlikely to happen if there are still Java services running in that stack. For instance ElasticSearch/OpenSearch is good at what it does (which is full-text search) but pumping massive amounts of logs into it is never going to be a light solution. Solutions such as Loki which just index tags and dump the raw content into an object storage bucket are the cheapest, and I guess ClickHouse ends up somewhere in the middle between those two depending on how well you configure it to fit the data. Or vice versa how well you can configure the data to fit the technical solution.
      - podoman 3y ago
        This is one of the reasons we’re considering moving off opensearch.
  - vadman97 3y ago
    We have had folks in our Discord successfully run highlight on a Raspberry Pi with 4GB RAM, so our recommendation is definitely on the safe side. We're running multiple infra services in the docker stack (postgres, opensearch, clickhouse, influxdb, kafka, redis) that we would look to consolidate in the future to help with running on leaner instances.

JimmyAustin 3y ago

Just about anything with only one instance is essentially hobby.

mrits 3y ago
Hard disagree. A hobby instance should be able to be spun up in the cloud on a free or near free tier.
KronisLV 3y ago
> Just about anything with only one instance is essentially hobby. Not high availability? Sure. However, I've seen software out there that ran as a monolith with a single deployment unit, facilitated lots of business processes and entire teams of people for continued development. Not everything necessarily needs high uptime, either. Some software can also serve particular time zones and have ample windows for scheduled maintenance, upgrades and so on. There's probably at least a few classifications between hobby projects on one end and HA distributed systems on the other. >> Cant say I would call these specs “hobby” at all With this, however, I'm inclined to agree. In my eyes, "hobby" would imply something more along the lines of: "Just give this half a CPU core and about 512 MB of RAM, maybe up to a GB of storage depending on what you'll use it for, it'll probably work well enough for a few users." Some software that mostly fits that definition, in my experience: Nextcloud, Apache2/Nginx/Caddy, Grav, Mattermost, Gitea, Heimdall, YOURLS, PrivateBin, phpBB, Uptime Kuma, Zabbix, PostgreSQL, MySQL/MariaDB, Redis, RabbitMQ, Docker Swarm and plenty others. Some software that needs more resources: SonarQube, PeerTube (for encoding), OpenProject (Ruby app), Sonatype Nexus (bloated Java app, but lots of functionality), Matomo (issues with displaying historic data with low resources), BackupPC (compresson of backups), K3s and other Kubernetes cluster distros and plenty others, too. Not to say that it somehow makes the software worse, just that people have different expectations. Perhaps more realistic expectations on my part for hobby software should be: "You should be able to launch it with whatever spare resources your laptop has."

deleted 3y ago

[deleted]

vadman97 3y ago

Apologies for the inconsistency here. Our Docker resource requirement recommendations were out of date after some recent improvements (https://github.com/highlight/highlight/pull/5074 https://github.com/highlight/highlight/pull/5074 and https://github.com/highlight/highlight/pull/4993 https://github.com/highlight/highlight/pull/4993). Just updated this: 8GB of RAM, 4 CPUs, and 64 GB of disk space.

that_guy_iain 3y ago
8GB of ram? For a hobby? Very resource intensive, eh?
- redskyluan 3y ago
  Totally agree with that. 8G might be too much to make the open source product popular. I would say 4G may more sense to me, I know how much engineering effort it requires though. LOL
  - wvh 3y ago
    Unlikely to happen if there are still Java services running in that stack. For instance ElasticSearch/OpenSearch is good at what it does (which is full-text search) but pumping massive amounts of logs into it is never going to be a light solution. Solutions such as Loki which just index tags and dump the raw content into an object storage bucket are the cheapest, and I guess ClickHouse ends up somewhere in the middle between those two depending on how well you configure it to fit the data. Or vice versa how well you can configure the data to fit the technical solution.
    - podoman 3y ago
      This is one of the reasons we’re considering moving off opensearch.
- vadman97 3y ago
  We have had folks in our Discord successfully run highlight on a Raspberry Pi with 4GB RAM, so our recommendation is definitely on the safe side. We're running multiple infra services in the docker stack (postgres, opensearch, clickhouse, influxdb, kafka, redis) that we would look to consolidate in the future to help with running on leaner instances.