New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
The Debian Lowend Myth
[root@berry:~] cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
[root@berry:~] pstree
systemd-+-2*[agetty]
|-crond
|-dbus-daemon
|-kthreadd/695---khelper/695
|-nginx---nginx
|-php-fpm
|-rsyslogd---2*[{rsyslogd}]
|-sshd---sshd---bash---pstree
|-systemd-journal
|-systemd-logind
`-systemd-udevd
[root@berry:~] free -m
total used free shared buff/cache available
Mem: 64 8 28 2 26 11
Swap: 128 0 128
Debian isn't the only choice 
Comments
wow nice only 8 mb ram used :-O
I am sorry, but:
root@ts3-test:/# cat /etc/debian_version 7.8 root@ts3-test:/# pstree init-+-kthreadd/3318---khelper/3318 |-nginx---4*[nginx] |-php5-fpm---2*[php5-fpm] |-sshd `-vzctl---bash---pstree root@ts3-test:/# free -m total used free shared buffers cached Mem: 32 10 21 0 0 7 -/+ buffers/cache: 2 29 Swap: 0 0 0There is a difference between OpenVZ and KVM guys.
spoil sport!
Debian on OVZ lies about memory usage. Try ofree - https://github.com/sleddoggy/ofree
But so does CentOS
A side-by-side comparison for me shows Centos 7 using 3-4 MB more RAM than Debian 7. Damn good considering some usage is systemd and some is 64bit overhead.
^ omg is he trying to knock the planet off its axis?
The one Nokia should just replicate the Tsar Bomba.
But do hypervisors limit memory usage properly?
With OVZ you are actually checking only some userspace executables memory usage. It is not the OS, really, practically, there is no OS there, as the OS is the kernel, more or less, together with some libraries, but the CentOS distro includes a lot of stuff, you need to be a good surgeon to remove the bloat in order to trim it down to compare with debian, but then you will have more like a Linux From Scratch than any of the two.
By default, debian is slimmer than CentOS. If you go way beyond default to remove bloatware, there wont be a Debian or CentOS distro at all.
Comparing Debian 7 and CentOS 7 is really apples and oranges (systemd vs sysvinit, and 64bit-only CentOS). We need to see how a Debian 8 systemd, 64bit container compares...
My points remain, a stripped bare system with no kernel, is no distro at all, it really depends on how good are the people at stripping it.
I'm not really trying to strip anything bare. I'm simply interested in the usability of new versions of mainstream distros, particularly in the context of low-RAM OVZ containers. For years we could just bung Debian 6/7 on and be done with it. Now with the move to systemd (and the possible/eventual death of 32bit) it's more of a challenge. CentOS 7 is quite workable on 64MB RAM with some tweaking, but 64bit certainly increases PHP memory usage. Will try Debian 8 64bit soon for comparision. And I'm holding out hope for a Debian 8 32bit template....
I prefer Debian anyways. Much less complicated
yum updateis much less complicated thanapt-get update && apt-get upgradeWho cares :P People nowadays use desktop which has alerts and involves a few clicks to update if not set to do it automatically
Linus Torvalds is NOT happy with "any" distribution...
https://youtu.be/7SofmXIYvGM
apt-get is happy with 64meg yum isn't
If you remove plugins, it works.
Yup. It's fine on 64MB, just disable the default 'fastest mirror' plugin. And make sure your OpenVz provider uses vSwap and not the archaic 'burst', else you'll die a horrible death.
Does it still work on 64/32MB with vSwap=0?
CentOS is ways more RAM friendly than Debian on devices with more RAM and on the long run. (from experience)
[root@pad:~] vzctl set 122 --swap 0M --save UB limits were set successfully CT configuration saved to /etc/vz/conf/122.conf [root@pad:~] vzctl enter 122 entered into CT 122 [root@c7 /]# free -m total used free shared buff/cache available Mem: 64 10 4 0 49 28 Swap: 0 0 0 [root@c7 /]# yum update base | 3.6 kB 00:00:00 epel/x86_64/metalink | 9.1 kB 00:00:00 epel | 4.4 kB 00:00:00 extras | 3.4 kB 00:00:00 mysql-connectors-community | 2.5 kB 00:00:00 mysql-tools-community | 2.5 kB 00:00:00 mysql55-community | 2.5 kB 00:00:00 nginx | 2.9 kB 00:00:00 updates | 3.4 kB 00:00:00 vz-base | 951 B 00:00:00 vz-updates | 951 B 00:00:00 (1/3): epel/x86_64/group_gz | 169 kB 00:00:03 (2/3): updates/7/x86_64/primary_db | 2.5 MB 00:00:50 (3/3): epel/x86_64/primary_db | 3.7 MB 00:00:56 (1/2): epel/x86_64/updateinfo | 441 kB 00:00:07 (2/2): epel/x86_64/pkgtags | 1.6 MB 00:00:17 No packages marked for update [root@c7 /]#Usually, with any server, even if it has a good amount of RAM, I disable the fastest mirror plugin.
I absolutely hate it, it takes a good extra 30 seconds sometimes when it chooses the wrong mirror.
Can you quote how you do so ?
Use –disableplugin=fastestmirror with your yum command. Temporary fix. Or you can edit the .conf file located in yum plugins folder. fastestmirror.conf - change value 'enabled=1' to 'enabled=0'
After the edit file should look like this.
~ cat fastestmirror.conf [main] enabled=0 verbose=0 always_print_best_host = true socket_timeout=3 hostfilepath=timedhosts.txt maxhostfileage=10 maxthreads=15 exclude=.gov, facebookAfter updating also run a
~yum clean allyeah, I am also like, WTF? garr is half a ms away and it goes to Rome?
All roads lead to Rome...
Indeed it is! :P