mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5826] How to scale? #2283
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2283
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Breee on GitHub (Feb 3, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5826
I'm searching for information on how to scale hoppscotch components.
We host everything distributed in k8s
@roopepaajanen commented on GitHub (Feb 12, 2026):
Hi,
Our app was bottlenecking and returning timeout error at peak traffic. I was able to solve the issue by increasing cpu and memory limit + increasing the number of db connections in our values.yaml file. I left rate limit values to default.
CPU and Memory
I found out that you can modify the limit of database connections in your databaseUrl:
postgresql://name:password@host.net:port/dhname?schema=hps&connection_limit=20You can verify this in packages/hoppscotch-backend/src/prisma/prisma.service.ts