# Can i incrase number of threads to use in ntpd proccess?

**URL:** <https://community.ntppool.org/t/can-i-incrase-number-of-threads-to-use-in-ntpd-proccess/1159>\
**Category:** Server operators\
**Created:** [March 20, 2019, 12:09am UTC](https://community.ntppool.org/t/can-i-incrase-number-of-threads-to-use-in-ntpd-proccess/1159 "2019-03-20T00:09:03Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![littlejason99](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/littlejason99/32/242_2.png) [@littlejason99](https://community.ntppool.org/u/littlejason99)\
**Post date:** [April 3, 2019, 3:15pm UTC](https://community.ntppool.org/t/can-i-incrase-number-of-threads-to-use-in-ntpd-proccess/1159/20 "2019-04-03T15:15:14Z")

</div>

[Chrony vs NTPD comparison](https://chrony.tuxfamily.org/comparison.html)

Better is a matter of opinion I suppose. NTPD has been around a long time, has direct support for many (legacy) refclocks, and other good things. However the source code has really grown over the decades and is in serious need of a major overhaul.

Chrony is a more recent program, it’s also much leaner. It doesn’t have all the legacy support that NTPD has, it’s geared towards more modern OSes.

There is also [NTPsec](https://www.ntpsec.org/) which is a fork of NTPD that has been stripped down and removed a ton of the obsolete legacy code (thus like Chrony it also only builds on more modern OSes). As the name implies it is more security focused too, I believe they have also re-written a fair amount of code.

---

_[View the full topic](https://community.ntppool.org/t/can-i-incrase-number-of-threads-to-use-in-ntpd-proccess/1159)._