wireapp / wireapp/wire-server

Performance Requirement

Open
#1,885 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
2.8k
Forks
334
Avg merge
1d 7h
Merged PRs (30d)
50

Description

Hi there.
Thank you for your contribution.
I have deployed my own server and built the android app connected to my own server.
I am going to enable "Advanced / Maintain Connection to server" by default.
In this case, all the users will keep the WebSocket connection to my server.
If there are 200 users, would it make a big load on the server? What specs of the server would be needed?
Please kindly give me some comments.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review docs.wire.com and wire-server-deploy first, then identify where deployment capacity guidance belongs. Establish server-sizing guidance for 200 users maintaining WebSocket connections and document the assumptions and requirements; done means the question is answered with concrete specifications.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
backend, documentation, performance
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.