diff --git a/images/CreationOfQuestionsGraph.png b/images/CreationOfQuestionsGraph.png new file mode 100644 index 00000000..6c757422 Binary files /dev/null and b/images/CreationOfQuestionsGraph.png differ diff --git a/images/RequestsAndErrors.png b/images/RequestsAndErrors.png new file mode 100644 index 00000000..40c67136 Binary files /dev/null and b/images/RequestsAndErrors.png differ diff --git a/images/ResponsTimeNRequest.png b/images/ResponsTimeNRequest.png new file mode 100644 index 00000000..dd07152c Binary files /dev/null and b/images/ResponsTimeNRequest.png differ diff --git a/index.html b/index.html index 177b7c5b..91f54347 100644 --- a/index.html +++ b/index.html @@ -513,6 +513,7 @@

arc42 W
  • 11. Risks and Technical Debts
  • 12. Glossary
    • +
  • 13. Anex I: Load test
    • @@ -1556,13 +1557,41 @@

    12. Glossary

    +
    + + +
    +

    13. Anex I: Load test

    +
    +
    +
    +Response Time and Number of requests +
    +
    +
    +
    +Requests and results +
    +
    +
    +

    When performing a the load test for the login and single player game with 1000 users conecting over a minute, we found that less than a 5% of the response end in a KO. This KO are due to the creation and start of the game.

    +
    +
    +
    +Creating the game +
    +
    +
    +

    When we create the game we also create all the questions with wikidata query service. +To solve this problem we could look for more optimiced queries or change when the questions are created, once a day we could create a bunch of questions and sav e them in the database, with this approach, when creating a new game the questions would be selected from our local database.

    +