Replies: 1 comment
-
hey, thanks for the post :) I haven't tried it in such old systems. As you said setting You can also set (rdtsc_resync_interval) value a bit higher like |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Thanks again for the great software. On older systems with glibc < 2.17,
std::chrono::steady_clock::now()
is implemented as a syscall in libstdc++ instead of using the faster VDSO (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59177)With the default logger config, the logging thread consumes close to 100% cpu due to the syscalls in an almost tight loop. Setting
backend_thread_strict_log_timestamp_order=false
will stop theclock_gettime
syscalls in the logging thread or settingbackend_thread_sleep_duration
will reduce the frequency of calls.FWIW, I came across this when compiling quill in an environment created with conda forge, the version of glibc that their libstdc++ library uses is old, perhaps for compatibility reasons.
I am not sure if its the responsibility of your program to handle these types but that I would point out that they exist and are not uncommon.
Beta Was this translation helpful? Give feedback.
All reactions