Post AXuwJs1ufYkUpZrppo by errante@rot.gives
 (DIR) More posts by errante@rot.gives
 (DIR) Post #AXuthDZYROKQRT2nce by errante@rot.gives
       2023-07-21T10:49:58.782809Z
       
       0 likes, 0 repeats
       
       nanosecond collisions occur 5% of the time when threads poll cpu clock 😟
       
 (DIR) Post #AXuu2yX32csMALFLVI by errante@rot.gives
       2023-07-21T10:53:54.493736Z
       
       1 likes, 1 repeats
       
       > Between threads, approximately 5% of the absolute times were exactly the same as other threads.😟
       
 (DIR) Post #AXuuteLynMccvnBcga by caskd@rot.gives
       2023-07-21T10:57:38.799638Z
       
       0 likes, 0 repeats
       
       @errante is this with CLOCK_REALTIME?
       
 (DIR) Post #AXuutevQfYyihjlvwO by i@declin.eu
       2023-07-21T11:03:27.752756Z
       
       0 likes, 0 repeats
       
       @caskd @errante might as well link the repo https://github.com/evanj/nanocollisionthough i'm not too sure what's the 😟 about
       
 (DIR) Post #AXuv6jLJYYyKAa72kC by errante@rot.gives
       2023-07-21T10:57:55.590164Z
       
       0 likes, 0 repeats
       
       @caskd yes
       
 (DIR) Post #AXuv7sIbk5zgEkONsm by caskd@rot.gives
       2023-07-21T11:06:02.997785Z
       
       0 likes, 0 repeats
       
       @errante okay but why is this such a big deal, no one uses time for thread synchronisation and timekeeping at nanosecond level is costly so i would expect this happens...
       
 (DIR) Post #AXuvEsPLjjGIbKste4 by caskd@rot.gives
       2023-07-21T11:07:18.891626Z
       
       0 likes, 0 repeats
       
       @errante unless you have some realtime needs with nanosecond accuracy this isn't a big deal at all
       
 (DIR) Post #AXuvHnAjew7REQRHUm by i@declin.eu
       2023-07-21T11:07:49.106237Z
       
       1 likes, 0 repeats
       
       @caskd @errante apart from maybe google/facebook, who tend to use time certainty ranges supplied by atomic clocks for that
       
 (DIR) Post #AXuvuqR5SUiMeDi1bM by errante@rot.gives
       2023-07-21T11:14:52.692103Z
       
       0 likes, 0 repeats
       
       @caskd you cant rely on monocity across threads
       
 (DIR) Post #AXuvxDfM3oTLH2VzkW by errante@rot.gives
       2023-07-21T11:15:18.655928Z
       
       0 likes, 0 repeats
       
       @i @caskd i thought collision rate would be lower
       
 (DIR) Post #AXuwJs1ufYkUpZrppo by errante@rot.gives
       2023-07-21T11:19:23.143184Z
       
       0 likes, 0 repeats
       
       @roboneko nothing, but i was under the assumption that timekeeping was better than it was
       
 (DIR) Post #AXuwfMHZO0iwjrR9AO by caskd@rot.gives
       2023-07-21T11:23:18.215308Z
       
       0 likes, 0 repeats
       
       @errante but it is monotonic what the fuck do you mean```CLOCK_MONOTONIC variants guarantee that the time returned by              consecutive calls will not go backwards, but successive calls              may—depending on the architecture—return identical (not-              increased) time values.```
       
 (DIR) Post #AXuwnfQw4DDgS2mOlU by errante@rot.gives
       2023-07-21T11:24:43.674666Z
       
       0 likes, 0 repeats
       
       @caskd doesnt monotonic mean always increasing?
       
 (DIR) Post #AXuwoYZh3LuBT8IfYG by caskd@rot.gives
       2023-07-21T11:24:58.183427Z
       
       0 likes, 0 repeats
       
       @errante bitch https://en.wikipedia.org/wiki/Monotonic_function
       
 (DIR) Post #AXuwwHy2gMzmHMNNVQ by errante@rot.gives
       2023-07-21T11:26:19.917275Z
       
       0 likes, 0 repeats
       
       @caskd yea dw im retarged
       
 (DIR) Post #AXux0qob3sarW18KZc by caskd@rot.gives
       2023-07-21T11:27:11.521735Z
       
       0 likes, 0 repeats
       
       @errante yeah same bby