Use VM to test the Scalability of our Project

phildree commented 1 year ago

User story

As a User
I want a well scaling software
So that it can cope with my needs

Acceptance criteria

Use the AWS VM to test the UI and Endpoints for Performance

Definition of done (DoD)

Feature is done when the acceptance criteria are fullfiled
Feature is done when there are test where it is necessary and they pass
Feature is done when the linter passes
Feature is done when it is merged onto our main branch (after the code has been reviewed by at least one other person)
Feature is done when the code has been documentend or commented properly

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

jnsrnhld commented 1 year ago

@phildree @MPSebastian I was wondering why this ticket was not part of the sprint backlog - I guess we just forgot to put it there?

jnsrnhld commented 1 year ago

Results:

Amount of topics	Frontend	Backend	Caching enabled
2500	25s	18s	false
5000	40s	20s	false
2500	3s	180ms	true
5000	6s	200ms	true

~150ms are network traffic overhead. On the same machine, querying the backend only takes 10-20ms with caching enabled.

The frontend produces a huge overhead while rendering all topics.

jnsrnhld commented 1 year ago

Rendering the topic search / bullet point list seems to be broken if the number of topics is > 2-3k. Also, request timeout is too low for the initial page buildup:

amosproj / amos2023ss01-apache-pulsar-ui