My (public) ElectrumX server became too popular, and now it often throttles and doesn't let me connect!
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 568
- Forks
- 447
- PR merge metrics
- No merged PRs in 30d
Description
I have 48GB RAM, and lots of it allocated to ElectrumX (as per the recommended max in the docs), so resources are not an issue. I also have 1000 sessions limit. Often 700 users or more connected. This seems fine as far as server load is concerned, but the throttling begins frequently anyway.
How can I either:
- solve this, so no throttling happens at all (unless the server runs out of RAM)
- or, alternatively, at least prioritize my OWN connection to the server, it is super frustrating getting throttled off my own server (haha..)
Please give any advice you might have, otherwise, I will just make it all private and only for me, but I would like to avoid that, as long as I have spare server capacity to burn for the good of the network.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the throttling with a public ElectrumX server supporting roughly 700 concurrent users, then review the server's throttling, session-limit, and memory settings alongside the documented recommended limits. Done should mean identifying why connections are throttled despite available RAM and documenting or implementing a way to avoid that behavior or prioritize the operator's connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100