WeSearch
Highest Random Weight in Elixir

Highest Random Weight in Elixir

https://jola.dev/about· ·7 min read · 0 reactions · 0 comments · 40 views
More from jola.dev programming Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

The article discusses the concept of Highest Random Weight (HRW) hashing in Elixir, highlighting its simplicity and stateless nature compared to traditional consistent hashing methods like ExHashRing. While HRW offers ease of use and avoids state management, it has a performance drawback with larger node lists due to its linear time complexity. The author provides benchmarks and comparisons between HRW and ExHashRing, noting that for smaller node counts, the performance difference is minimal.

Key facts
How this story was covered

2 outlets in our directory ran this story, first to last over 19 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
jola.dev · https://jola.dev/about
Read full at jola.dev →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherjola.dev
Canonical URLhttps://jola.dev/posts/highest-random-weight-in-elixir
Publication timeFri, 22 May 2026 09:27:23 +0000
Retrieval time2026-05-22T09:32:01.321Z
Last seen2026-05-22T09:32:01.321Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterps6CTweeXym7 · 2 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Highest Random Weight in Elixir May 21, 2026 15 min read elixir hrw oss Consistent hashing is a common building block for distributed Elixir and enables fairly low complexity and high value design patterns, like the distributed rate limiter or cache. I’ve written about it before. The most common way of assigning keys to nodes, ensuring that any node participating in the cluster can figure out which node owns the given key, is Discord’s ExHashRing. This is an incredibly battle-tested and reliable library with excellent performance characteristics, and I’ve only had good experiences with it. That said, it does have a downside. You have to start and manage the ring processes.

Excerpt limited to ~120 words for fair-use compliance. The full article is at jola.dev.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from jola.dev