You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2026/10/20 18:32:00 UTC
[jira] [Resolved] (IMPALA-15585) OsInfo does not understand that ARM's CLOCK_MONOTONIC is fast
[ https://issues.apache.org/jira/browse/IMPALA-15585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-15585.
------------------------------------
Fix Version/s: Impala 5.1.0
Resolution: Fixed
> OsInfo does not understand that ARM's CLOCK_MONOTONIC is fast
> -------------------------------------------------------------
>
> Key: IMPALA-15585
> URL: https://issues.apache.org/jira/browse/IMPALA-15585
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 5.1.0
>
>
> OsInfo::Init() has logic to detect whether the clock_gettime has a fast CLOCK_MONOTONIC implementation. If it does not detect a fast implementation, it uses CLOCK_MONOTONIC_COARSE, which has significantly lower resolution. This is to protect against old clock implementations that are very slow (see IMPALA-2407). ARM has a high precision clocksource with equivalent speed to x86_64 for CLOCK_MONOTONIC, but it has a different name in the clocksource file. The algorithm doesn't detect it and uses the coarse timer. This makes time counters in ARM profiles much less useful.
> We should update the detection to properly detect this on ARM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)