News for hackers. Stuff that matters.
Re:Ntimed – NTPD replacement by lazyjones on Monday December 22, 2014 @04:27AM (#8782538)
> Assume NTPD uses 0.1% of machine resources -> 500 fully loaded servers.

Bold assumption. It uses 0.0006% on my slow 6 years old box (over 13 days uptime). Let's be generous and say it's 0.001%, then you get 1.1 ton of CO2, which is the equivalent of the production of about 32.8 Kg of beef. I don't think such dramatic conclusions can be made from those facts.

Re:Ntimed – NTPD replacement by phkamp on Monday December 22, 2014 @04:54AM (#8782579)
First, I doubt your kernels statistics actually account correctly at that level of precision. (If it does, that alone would waste a lot of CPU cycles!)

Second, have you checked the memory footprint of NTPD ? "machine resources" is more than CPU cycles.

And don't forget: That number was one quarters purchase of servers, running for half a year. All the servers bought in 2010, 2011, 2012, 2013 and the other half of the year were not included.

Things add up.

Re:Ntimed – NTPD replacement by lazyjones on Monday December 22, 2014 @11:34AM (#8783705)
> Second, have you checked the memory footprint of NTPD ? "machine resources" is more than CPU cycles.

284K, which is a whopping 0.04% of available memory. I don't see how this increases CO2 output though.

> Things add up

To a still very insignificant number, dwarfed by the beef consumption of the people reading this.

I'd say there are better arguments in favour of using dated languages than this.

Re:Ntimed – NTPD replacement by phkamp on Monday December 22, 2014 @02:25PM (#8784610)
I can't change how much beef people eat.

I can change how their computers synchronize time.