How setting the TZ environment variable avoids thousands of system calls
blog.packagecloud.io
How setting the TZ environment variable avoids thousands of system calls
1–10 of 148 posts
Re: How setting the TZ environment variable avoids thousands of system calls
#2http://mail-archives.apache.org/mod_mbox/httpd-dev/201111.mb...
https://github.com/apache/httpd/blob/trunk/server/util_time....
The internals of glibc can often be pretty surprising sometimes, I'd really encourage people to go spelunking into the glibc source when they are profiling applications.
Re: How setting the TZ environment variable avoids thousands of system calls
#3Re: How setting the TZ environment variable avoids thousands of system calls
#4does anyone know if this impacts docker images as well ?
Re: How setting the TZ environment variable avoids thousands of system calls
#5does anyone know if this impacts docker images as well ?
Re: How setting the TZ environment variable avoids thousands of system calls
#6does anyone know if this impacts docker images as well ?
It looks like musl, which is used on Alpine Linux images for example, will only read it once, and then cache it:
https://github.com/esmil/musl/blob/master/src/time/__tz.c#L1...
It has a mutex/lock around the use of the TZ info, but avoids re-stat'ing the localtime file.
Re: How setting the TZ environment variable avoids thousands of system calls
#7Re: How setting the TZ environment variable avoids thousands of system calls
#8Re: How setting the TZ environment variable avoids thousands of system calls
#9Side note - why do some sites completely hide information about who is behind them? I couldn't find a single thing about that on their blog or main site.
I'm under the impression that he may also write a lot these himself? Not entirely certain, though.
Re: How setting the TZ environment variable avoids thousands of system calls
#10Side note - why do some sites completely hide information about who is behind them? I couldn't find a single thing about that on their blog or main site.