Discussion
Loading...

Discussion

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Stefano Marinelli
@stefano@mastodon.bsd.cafe  ·  activity timestamp 3 days ago

RE: https://mastodon.social/@nixCraft/115566280074527897

"Just" 270 MB for...an idle server?
Debian is still a great distributions but let's measure the ram consumption of a freshly installed *BSD or Illumos based server. The numbers are totally different.

#RunBSD #illumos #FreeBSD #OpenBSD #NetBSD #DragonflyBSD

  • Copy link
  • Flag this post
  • Block
Alex Stade
@astade@mastodon.social replied  ·  activity timestamp 2 days ago

@stefano I have never understood the wonders of systemd and Linux memory management. To me it’s a Wild West situation.

  • Copy link
  • Flag this comment
  • Block
Pete Orrall
@peteorrall@mastodon.bsd.cafe replied  ·  activity timestamp 3 days ago

@stefano I think if we are going to be analyzing RAM usage across OSes, then usage needs to be recorded every X minutes over a specific workload, with idle being baseline or control group. Just showing 270MB RAM at idle and then another single snapshot at 10GB of some kind of workload still doesn't tell much. It's difficult to infer anything else.

  • Copy link
  • Flag this comment
  • Block
JdeBP
@JdeBP@tty0.social replied  ·  activity timestamp 3 days ago

@stefano

In fairness, it is not "just booting". The screenshot shows exim and an unattended-upgrades script started up.

The world has still yet to shake the idea that every single server in the normal case needs a standalone, monolithic, local queue/delivery, mail system running; it seems.

I wonder why systemd-timesyncd has a larger VIRT value than anything else there.

#Debian #systemd #exim #MorrisWorm

  • Copy link
  • Flag this comment
  • Block
these machines will destroy US.
@cienmilojos@infosec.exchange replied  ·  activity timestamp 3 days ago

@stefano none of this matters to measure with nothing running. An idle server with nothing running is a waste of compute. Servers best unit of measure is typically uptime and power usage. Willing to bet both Debian and BSD manage the task far more efficiently than a Windows server.

  • Copy link
  • Flag this comment
  • Block
Stefano Marinelli
@stefano@mastodon.bsd.cafe replied  ·  activity timestamp 3 days ago

@cienmilojos I know. But if the idle, useless system is using 270 MB for doing nothing, every single service will raise that number. IMHO, an idle server (freshly installed) should use some MB of ram, not hundreds. Let's not talk about GBs...

  • Copy link
  • Flag this comment
  • Block
Tim Chase
@gumnos@mastodon.bsd.cafe replied  ·  activity timestamp 3 days ago

@stefano curious what your other fresh installs rank in at.

A fairly fresh FreeBSD install on my MassiveGrid VM according to top(1):
7044K Active
109M Inact
1572M Wired
2232M Free
ARC: 1238M Total, 498M MFU, 654M MRU, 512K Anon, 9920K Header, 70M Other

And a fairly fresh OpenBSD install on a RackNerd VM:
Real: 29M/1210M act/tot
Free: 743M
Cache: 380M

I'm never quite certain how to measure RAM consumption though.

  • Copy link
  • Flag this comment
  • Block
nia
@washbear@mastodon.sdf.org replied  ·  activity timestamp 3 days ago

@stefano you can't compare the memory usage of different unix variants easily because they all use and account for caching differently anyway.

netbsd will be using 32mb and then top will report that "2gb" is in use after /etc/daily runs

  • Copy link
  • Flag this comment
  • Block
Stefano Marinelli
@stefano@mastodon.bsd.cafe replied  ·  activity timestamp 3 days ago

@washbear of course. But I've recently tested Raspbian vs NetBSD on an old Raspberry Pi A+. Raspbian was almost unusable, swapping all the time. NetBSD is totally usable - I'm not talking about desktop, of course.

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login