Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fhevm-listener: Do TRIGGER/NOTIFY in postgresq instead of NOTIFY in listener #336

Open
rudy-6-4 opened this issue Feb 21, 2025 · 0 comments · May be fixed by #354
Open

fhevm-listener: Do TRIGGER/NOTIFY in postgresq instead of NOTIFY in listener #336

rudy-6-4 opened this issue Feb 21, 2025 · 0 comments · May be fixed by #354
Assignees
@rudy-6-4
Labels
enhancement New feature or request

Comments

@rudy-6-4
Copy link
Contributor

rudy-6-4 commented Feb 21, 2025 •
edited
Loading

Goal:
- reduce the network load on the listener/database.
- reduce the latency of scheduling events by removing an intermediate for NOTIFY

Currently the new fhevm-listener sends a NOTIFY for each row inserted.

This can be delegated to the database directly:

  • simplify code
  • remove a network interaction x the number of listener for redundancy: reduce latency of scheduling and the network load of DB
@rudy-6-4 rudy-6-4 added the enhancement New feature or request label Feb 21, 2025
@rudy-6-4 rudy-6-4 changed the title Use TRIGGER in postgresq instead of NOTIFY in fhevm-listener fhevm-listener: Do TRIGGER/NOTIFY in postgresq instead of NOTIFY in listener Feb 21, 2025
@rudy-6-4 rudy-6-4 self-assigned this Mar 3, 2025
@rudy-6-4 rudy-6-4 linked a pull request Mar 3, 2025 that will close this issue
Rudy/fhevm listener auto notify directly on db #354
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rudy-6-4 rudy-6-4

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rudy/fhevm listener auto notify directly on db zama-ai/httpz-backend
1 participant
@rudy-6-4