Skip to content

Upgrade scheduler to ferroid 3 - #2899

Open
s0l0ist wants to merge 2 commits into
apache:mainfrom
s0l0ist:chore/upgrade-ferroid-3.1.0
Open

s0l0ist wants to merge 2 commits into
apache:mainfrom
s0l0ist:chore/upgrade-ferroid-3.1.0

Conversation

@s0l0ist

@s0l0ist s0l0ist commented Nov 19, 2026 •

Copy link
Copy Markdown

Which issue does this PR close?

N/A

Rationale for this change

Upgrade the scheduler to ferroid 3.x. The latest version has substantial performance improvements for Base32 encoding.

What changes are included in this PR?

Update the ferroid dependency, adapt job ID generation to the v3 clock, async, and base32 APIs, and refresh the lockfile.

Are there any user-facing changes?

No

s0l0ist and others added 2 commits November 19, 2026 23:34
Adapt job ID generation to the v3 clock, async, and base32 APIs and refresh the lockfile.

@milenkovicm milenkovicm left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @s0l0ist update makes sense, one comment inline

/// which does not capture machine id as part result.
pub(crate) struct DefaultJobGenerator {
generator: AtomicSnowflakeGenerator<SnowflakeMastodonId, MonotonicClock>,
generator: AtomicSnowflakeGenerator<SnowflakeMastodonId, CachedClock>,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CachedClock or DirectClock 🤔 starting a thread or reading time on every call?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants