I had a batch importer stamping DateTime.Now onto every row it processed. A few hundred thousand rows, one timestamp each, nothing I'd ever think twice about. Then I put a profiler on the thing because it was slower than it had any right to be, and there it was near the top: reading the clock. Not the database, not the parsing. The clock.
So I did the thing I always end up doing. I counted.
Now is UtcNow wearing a coat
DateTime.Now doesn't read a "local clock." There's no such thing. It reads UTC, exactly like DateTime.UtcNow does, and then converts that instant into local time using TimeZoneInfo.Local . That conversion is the whole difference between the two calls. One reads the clock. The other reads the clock and then asks the time zone database what your offset is right now, DST and all.
The offset lookup is the part that costs.…