Skip to content

Conversation

@rudy-6-4
Copy link
Contributor

@rudy-6-4 rudy-6-4 commented Dec 9, 2025

Compute chain dependency on the transaction level instead of ops level.

@cla-bot cla-bot bot added the cla-signed label Dec 9, 2025
for (age, log) in logs.iter().enumerate() {
let tx = log.transaction_hash.unwrap_or_default();
if let Some(handle) = tfhe_result_handle(&log.event) {
handle_to_tx.insert(handle, (age, tx));
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not sure if it's possible, but ideally this should be filtered to only include allowed handles.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is filtered for the past cache, but still needed here to detect internal dependency. Otherwise it could promote an old handle (several block before) as dependency chain vs the fresher one. But this policy could be changed if you think it's better the other way around for transaction internal dependency.r

…iple workers

It provides a non-blocking, distributed locking mechanism that
coordinates dependence-chain processing across multiple tfhe-workers.

A worker can acquire ownership of the next available dependence-chain entry for processing
ordered by last_updated_at (FIFO queue-like approach).

Ownership expires after a timeout, enabling work-stealing by other workers.

New CLI param --worker_id
- Added LockingReason for logging
- Make expiry configurable
@rudy-6-4 rudy-6-4 force-pushed the rudy/scaling/dependence_chain branch from 111dc67 to cf81b98 Compare December 10, 2025 08:33
@rudy-6-4 rudy-6-4 force-pushed the rudy/scaling/dependence_chain branch from cf81b98 to 5b28a38 Compare December 11, 2025 00:44
@mergify
Copy link

mergify bot commented Dec 11, 2025

🧪 CI Insights

Here's what we observed from your CI run for d7da475.

❌ Job Failures

Pipeline Job Health on main Retries 🔍 CI Insights 📄 Logs
coprocessor-cargo-test coprocessor-cargo-test/cargo-tests (bpr) Unknown 0 View View

@rudy-6-4 rudy-6-4 force-pushed the rudy/scaling/dependence_chain branch from 5b28a38 to 5298c04 Compare December 11, 2025 07:40
@rudy-6-4 rudy-6-4 changed the base branch from main to georgi/tfhe-worker/dependence_chain_id December 11, 2025 07:41
@rudy-6-4 rudy-6-4 force-pushed the rudy/scaling/dependence_chain branch from 5298c04 to d7da475 Compare December 11, 2025 07:59
@rudy-6-4 rudy-6-4 marked this pull request as ready for review December 11, 2025 08:03
@rudy-6-4 rudy-6-4 requested a review from a team as a code owner December 11, 2025 08:03
@goshawk-3 goshawk-3 force-pushed the georgi/tfhe-worker/dependence_chain_id branch from 4618e0d to b206f87 Compare December 11, 2025 13:29
@rudy-6-4 rudy-6-4 force-pushed the rudy/scaling/dependence_chain branch from d7da475 to f3b7192 Compare December 11, 2025 14:11
@rudy-6-4 rudy-6-4 changed the title fix(coprocessor): host-listener, dependency chain, step 1 fix(coprocessor): host-listener, dependency chain Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants