Scribd Logo
Upload

Welcome to Scribd!

  • 2022jun - Load Test Plan

    Uploaded by

    M. Apriyanto Wijaya
    6 views10 pages
    This document summarizes the requirements for load testing the FSI System web application. The application is a PHP web application built using Laravel with Nginx, MySQL, and other technologies. Key features to test include login, chat, file submission, and meeting registration. The SLA requirements include supporting 25 average concurrent users, 65 maximum users, response times between 3-45 seconds on average and 5-70 seconds maximum, and transaction rates of 63-117 per second. An analysis estimates load test scenarios for 1000 total users with peaks of 65 concurrent users to validate the application meets requirements.

    Original Description:

    Original Title

    2022Jun_Load Test Plan

    Copyright

    © © All Rights Reserved

    Available Formats

    XLSX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document summarizes the requirements for load testing the FSI System web application. The application is a PHP web application built using Laravel with Nginx, MySQL, and other technologies. Key features to test include login, chat, file submission, and meeting registration. The SLA requirements include supporting 25 average concurrent users, 65 maximum users, response times between 3-45 seconds on average and 5-70 seconds maximum, and transaction rates of 63-117 per second. An analysis estimates load test scenarios for 1000 total users with peaks of 65 concurrent users to validate the application meets requirements.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    6 views10 pages

    2022jun - Load Test Plan

    Uploaded by

    M. Apriyanto Wijaya
    This document summarizes the requirements for load testing the FSI System web application. The application is a PHP web application built using Laravel with Nginx, MySQL, and other technologies. Key features to test include login, chat, file submission, and meeting registration. The SLA requirements include supporting 25 average concurrent users, 65 maximum users, response times between 3-45 seconds on average and 5-70 seconds maximum, and transaction rates of 63-117 per second. An analysis estimates load test scenarios for 1000 total users with peaks of 65 concurrent users to validate the application meets requirements.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 10

    No Description

    1 Application Name
    2 Application type (Web, Mobile Android/IoS)

    3 Number of Feature to Test

    4 SLA for Application to Test:


    Average Concurrent User
    Maximum Concurrent User

    Average Response Times

    Maximum Response Times

    Average Transaction per Seconds


    Maximum Transaction per Seconds
    5 Application Architecture:
    Programming Languange (ex:php,python,Java, etc)
    Web Server in use (ex:Apache,Nginx,etc)
    Database server in use (ex:mssql,mysql,mariadb,etc)
    Other component info (using ftp,api,http/https,etc)
    Comment / Remark

    FSI System (FIRST Virtual Office)


    Web Application

    * Descending order by no of high access


    - Login (clock-in) / Logout (clock-out)
    - Private chat / Group chat
    - Move area/ floor
    - Meeting registration
    - File submission

    99.95%
    25 users
    65 users

    3 sec / page

    45 sec

    5 sec / page

    70 sec / page
    63 times / sec
    117 times / sec
    *Can provide the architecture after the contract
    PHP v.8.0.0
    Nginx
    MySQL v.8.0.0
    Laravel v.8.4.0
    Laravel Web Sockets
    Laravel Stancl/Tenancy
    Vue JS
    Tailwind CSS
    Composer
    API Google Cloud Storage
    API Zoom
    API SendGrid
    SPA Path Finding
    Calculation

    Test Scinario:
    1. Users login(clock-in) : avg 2.35 sec
    2. Open chat window clicking to another avatar : avg 1.87sec
    3. Send chat : avg 43.19 sec
    * The avg execution time of No.1 - No.3 (3 steps) is for 50 secs.
    **.The max execution time of No.1 - No.3 (3 steps) is for 75 secs.
    -----------------------------------------------------------------------------------------------------------
    A. User : 1000 users
    B. DAU : 800 users (7:00-22:00)
    C. Play Time per User : 30 mins
    D. Accees Interval : 70 sec (15 hours * 60 mins * 60 sec / B.800 users = 67.5 =>70 sec)
    E. Access Duration Time :1800 sec (C. 30mins * 60 sec)
    F. Concurrent Access User : 25 users (E.1800 sec / D.70 sec)
    G. Peak Access Ratio : 2.5 times
    H. Peak Access User : 65 users (F.25 users * H.2.5 times = 62.5=>65 users)
    I. No of Server Access : 252 times
    1. Users login(clock-in) : 38 requests
    2. Open Chat Click Avatar: 104 requests
    3. Send Chat: 110 requests
    J. Server Access Interval : 7 sec (E.1800 sec / 252 times)
    K. Concurrent Request Times :10 times (H.65 users / J.7 sec = 9.3=>10 times)
    L. Transaction Rate : 50 % (TBC)
    M. Transaction Request : 126 times ( I.252 times * L.50% )
    N. Transaction per Sec : 63 times (F.25 users * M.126 times / 50 sec )
    O. Peak Transaction per Sec : 117 times (H.65 users * M.126 times / 70 sec )

    F. Concurrent Access User : 25 users (E.1800 sec / D.70 sec)


    H. Peak Access User : 65 users (F.25 users * H.2.5 times = 62.5=>65 users)
    1. Users login(clock-in) : avg 2.35 sec
    2. Open chat window clicking to another avatar : avg 1.87sec
    3. Send chat : avg 43.19 sec
    1. Users login(clock-in)
    2. Open Chat Click Avatar
    3. Send Chat
    N. Transaction per Sec : 63 times (F.25 users * M.126 times / 50 sec )
    O. Peak Transaction per Sec : 117 times (H.65 users * M.126 times / 70 sec )
    Workspace

    Chat Screen
    Calendar (Meeting , Leave schedule)

    You might also like