Skip to content

Commit

Permalink
Update software_metrics.md
Browse files Browse the repository at this point in the history
  • Loading branch information
sfrancisw committed Jun 30, 2024
1 parent 35736ec commit aedf26a
Showing 1 changed file with 12 additions and 2 deletions.
14 changes: 12 additions & 2 deletions Documentation/software_metrics.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,26 @@
# Project Name
## Measurements
### Introduction
This section introduce which metrics are measured for your project. How are they measured? By which software?
We measured three metrics for our website which are listed below. The page load time is measured by the website [pingdom](https://www.pingdom.com/) that was also presented during one of our lectures. The measurement for user traffic and server load is taking digital ocean, the platform that our website runs on.
#### Page Load Time​
Our page load performance is quite good with an rating of 88. It's rather quick with a loadtime of around half a second and has a size of only 2mb.

![image](https://github.com/SE-TINF22B6/time2shine/assets/49996344/a5680c23-3b90-4cf1-810d-98476f96eaee)

#### User Traffic
The second metric measures the user traffic by time. It is clearly visible that the user traffic currently is rather consistent with some ups and downs, apart from the major drop between 12pm and 06am.

![image](https://github.com/SE-TINF22B6/time2shine/assets/49996344/e928f2df-7803-4973-be2c-a8c3daf2ace7)

#### Server Load
The server load shows the cpu usage that is required. We hosted our project on a sever with a rather big cpu cap, since nothing spoke against it. Therefore, there aren't any spikes above the 20% mark which is good.

![image](https://github.com/SE-TINF22B6/time2shine/assets/49996344/27b441a2-2cde-4566-9db1-5e1466192d94)


### 2. Measure results and analysis
This section summarizes measure results and any analysis/observations during development.
Given the fact that our website has a pretty big trailer video that has to be loaded too, the overall page load time seems good. In general when testing the website, it doesn't feel slow and no problems are detected when loading the website.

Since the website was still in development, we can assume that a total response of 676 within 24 hours is rather low since one could imagine that the play rate will only really start once the website is fully developed. Depending on the "success" of our website and whether or not people all around the world will play game on it, the big drop at night might flatten out due to different timezones and the overall request across the day might become more evenly distributed.

We can also see that we still have a big margin for our cpu usage. This is because we have a pretty good deal for it at digital ocean and didn't have to pay for it, so there are no disadvatages in having this big of a margin. Therefore, we also won't have to wory about increasing our used cpu for the website for a rather long time.

0 comments on commit aedf26a

Please sign in to comment.