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.

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

[Cleanstr] [tech debt] High CPU usage issues with signature verification #18

Open
dcadenas opened this issue Oct 11, 2023 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@dcadenas
Copy link
Contributor

The moderator google cloud function checked signatures for each event to moderate. These are expensive CPU bound operations and @mplorentz discovered that we were incurring in high costs, I assume the signatures were the cause. For the moment I disabled the verification but this is not ideal. One alternative to consider is to host an instance in Google Cloud Engine and there host a Rust server that just does the Schnorr signature work needed. We could test with some feature flag and see if gives better results

@dcadenas dcadenas moved this to 📋 Backlog in Cleanstr Oct 11, 2023
@dcadenas dcadenas removed this from Cleanstr Nov 22, 2023
@dcadenas dcadenas moved this to Delivery Backlog in Verse: Nos Projects Nov 22, 2023
@setch-l setch-l changed the title High CPU usage issues with signature verification [Cleanstr] [tech debt] High CPU usage issues with signature verification Dec 11, 2023
@setch-l setch-l moved this from Delivery Backlog to Next in Verse: Nos Projects Dec 15, 2023
@setch-l setch-l moved this from Next to Dev Sprint in Verse: Nos Projects Dec 18, 2023
@setch-l setch-l added the bug Something isn't working label Dec 18, 2023
@setch-l setch-l moved this from Dev Sprint to Next in Verse: Nos Projects Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Next
Development

No branches or pull requests

2 participants