Server Performance - nginx & ntp

Hello everyone!
Its being a long time, hope everyone of you is doing well..

I am having some difficultly in understanding the following parameters for nginx,
Scenario (nginx is used for serving static content )

proxy_buffer_size 4k
proxy_buffers 16 32k
proxy_busy_buffers_size 64k
proxy_buffering off

I like to know if i exceed the proxy_buffer_size to lets say 128 and proxy_buffers to 4 256 does it affects nginx performance in anyway ?

if proxy_buffering is set to off, does proxy_buffers value in anyway has any affect on nginx ?

---------------
NTP related,

At times i have noticed that ntpd daemon stucks and eats away computer resources, for that i have found a solution to remove iburst and restart services, ( aggressiveness for brining in time sync slows down if ntp server does not respond ) I like to know if that solution is legit ?

Can 4 different NTP servers of different types like redhat,centos,debian,X be coupled together, the reason for coupling different ntp servers is to have better redundancy incase of either fails (not sure if this is the right approach) or is there any better approach to it ?

Thanks

NTP related,

At times i have noticed that ntpd daemon stucks and eats away computer resources, for that i have found a solution to remove iburst and restart services, ( aggressiveness for brining in time sync slows down if ntp server does not respond ) I like to know if that solution is legit ?

When your NTP server is unresponsive, the iburst mode would continue to send queries until the server responds and time synchronization starts. It send a burst of eight packets in place of the usual one for 'Unreachable Server'. So if your network is finicky, iburst mode would make ntpd to get stuck. Yes, the solution you found is something I'd do.

Can 4 different NTP servers of different types like redhat,centos,debian,X be coupled together, the reason for coupling different ntp servers is to have better redundancy incase of either fails (not sure if this is the right approach) or is there any better approach to it ?

Different providers such as Debian/Redhat etc would just sync their NTP servers with global NTP servers serving at a high stratum level. I have no idea if they actually own stratum 0 servers (the one with an atomic clock ). Yeah, sure u can club as many ntp servers as you want, but you'll want to connect to an NTP server that is geographically closest to you. Check this out.

Originally Posted by Honest Abe When your NTP server is unresponsive, the iburst mode would continue to send queries until the server responds and time synchronization starts. It send a burst of eight packets in place of the usual one for 'Unreachable Server'. So if your network is finicky, iburst mode would make ntpd to get stuck. Yes, the solution you found is something I'd do. Different providers such as Debian/Redhat etc would just sync their NTP servers with global NTP servers serving at a high stratum level. I have no idea if they actually own stratum 0 servers (the one with an atomic clock ). Yeah, sure u can club as many ntp servers as you want, but you'll want to connect to an NTP server that is geographically closest to you. Check this out.

Thank you for the pointers, I will surely look into it.

You're welcome. Take a look at chrony too.
See https://chrony.tuxfamily.org/comparison.html