Killing O(n): How Timing Wheels Expire 10 Million Keys Effortlessly in Golang https://medium.com/@ankur_anand/killing-o-n-how-timing-wheels-expire-10-million-keys-effortlessly-in-golang-9a6b8709fd91
Signed Maxim Babichev

Channel
@phpdev_ru
On this record: Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001300655366 |
|---|---|
| Type | Channel |
| Username | @phpdev_ru |
| Description | Awesome: https://github.com/ziadoz/awesome-php Контакты с администрацией: email: info@babichev.net site: https://babichev.net phone: +79183822970 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/phpdev_ru |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:17 | 9 | no change |
| 7 Aug 2026, 22:58 | 9 | first reading |
15 posts held, back to 10 July 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 2 November 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| LjN8KYrbd | 1 | 26 July 2024 | 26 July 2024 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 15 most recent posts we hold, published 10 July 2024 to 2 November 2025. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Killing O(n): How Timing Wheels Expire 10 Million Keys Effortlessly in Golang https://medium.com/@ankur_anand/killing-o-n-how-timing-wheels-expire-10-million-keys-effortlessly-in-golang-9a6b8709fd91
Signed Maxim Babichev
https://www.youtube.com/watch?v=DbgBTeO83qY
Signed Maxim Babichev
https://skoredin.pro/blog/golang/cpu-cache-friendly-go
Signed Maxim Babichev
Bloom filters The original motivation for the creation of Bloom filters is efficient set membership, using a probabilistic approach to significantly reduce the time and space required to reject items that are not members in a certain set. The data structure was proposed by Burton Bloom in a 1970 paper titled "Space/Time Trade-offs in Hash Coding with Allowable Errors". It's a good paper that's worth reading. https…
Signed Maxim Babichev
https://habr.com/ru/articles/891426/
Signed Maxim Babichev
https://jonas.github.io/tig/doc/tig.1.html
Signed Maxim Babichev
https://habr.com/ru/companies/vk/articles/476276/
Signed Maxim Babichev
📨 Запуск SMTP-сервера — это на 50% написание кода и на 50% работа с настройками DKIM, SPF и DMARC. В этой статье кофаундер Valyent Alexis Bouchez рассматривает обе стороны. Библиотека go-smtp в конечном итоге выполняет тяжелую работу. 👉 Читать гайд
Signed Maxim Babichev
🛠 LinDB — масштабируемая, высокопроизводительная и высокодоступная распределенная база данных временных рядов на базе Go К линейке систем баз данных на базе Go присоединяется LinDB — новая база данных временных рядов, ориентированная на производительность и доступность, доступ к которой можно получить через REST API. 👩💻 GitHub
Signed Maxim Babichev
Открыт приём заявок на бесплатный курс Route 256 от Ozon Tech Подойдёт тем, кто: — Хочет сменить стек и перейти на Go — Уже пишет на Go, но хочет углубить и расширить свои знания Что будет: 2 месяца вебинаров, воркшопов и код-ревью домашних заданий. Решение e-com-кейсов, уникальные сервисы и постоянная практика на современном стеке. Как попасть: пройти отборочный контест 11 августа. Оставить заявку стоит уже сейчас…
Signed Maxim Babichev
https://habr.com/ru/companies/karuna/articles/830346/
Signed Maxim Babichev
https://antonz.org/go-1-23/
Signed Maxim Babichev
Showing the 12 most recent of 15 posts we hold for @phpdev_ru. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“[RU] PHP/Go Developers” (@phpdev_ru), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/phpdev_ru.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.