Clarification on cProfile Timing Resolution and the ".001 seconds" Clock Tick Statement

Documentation
5

@barry-scott @elis.byberi

Thank you very much! I understand the difference between the clock tick rate and reported resolution. On my environment, the clock rate is about every 100ns, which is much higher than 1ns. However, still, the orders of magnitude (10000x) gap between this measurement and the statement in the docs, which made me still confused

h-ishida@umejuice:~/tmp/tmp$ cat tmp.py 
import time

for _ in range(10):
    clock = time.CLOCK_MONOTONIC
    t1 = time.clock_gettime_ns(clock)
    while True:
        t2 = time.clock_gettime_ns(clock)
        if t2 != t1:
            break
    delta_ns = t2 - t1
    print(f"Observed tick: {delta_ns} ns")
h-ishida@umejuice:~/tmp/tmp$ python3 tmp.py 
Observed tick: 390 ns
Observed tick: 151 ns
Observed tick: 150 ns
Observed tick: 90 ns
Observed tick: 111 ns
Observed tick: 110 ns
Observed tick: 90 ns
Observed tick: 80 ns
Observed tick: 100 ns
Observed tick: 100 ns