Hacker News new | past | comments | ask | show | jobs | submit login

This.

UTC is not only unambiguous, but on some systems measurably faster to capture.

My experience has taught me to work in UTC everywhere possible, local time is typically only relevant for direct human interaction.




A caveat here as well is you also need to make sure your various clocks in the data center are synched. This is one of those common but overlooked scenarios which lead to hilarious discussions about latency when really there was just a clock synch problem. Additionally the fallacies of distributed computing come into play here (namely, transport cost is 0) so you need to take extra care when looking at measurements across different systems and machines. Even machines in the same data center. The pipe that you are communicating across could be oversubscribed for example.


Yes. But you get all those problems plus more, if you convert to local time first.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: