Skip to main content

Welcome to the Cyara Knowledge Center

Search

How do I calculate Ramp Up Time, CAPS and Call Duration?

Updated: Valery Topilin Edited:

Answer

Ports, Ramp Up Time, Call Duration and Call Attempts Per Second (CAPS) are related to each other with the following expressions:

Ports = Call Duration * CAPS

Ramp Up Time = Ports / CAPS

It's easy to see that Ramp Up Time in these expressions equals Call Duration. It is true when desired CAPS during the Ramp Up stage is the same as CAPS during the Sustain Load stage .

Examples:

1000 Ports load test with target CAPS of 20 (call attempts per second)

1. What is my Ramp up time if I do not want to exceed 20 CAPS?

Ramp Up Time = 1000/20 = 50 seconds

2. What is the minimal Call Duration needed to reach 1000 ports?

Call Duration = 1000/20 = 50 seconds

3. What if I want to Ramp Up faster and get to 1000 ports in 10 seconds? What would be my CAPS during Ramp Up period?

CAPS = 1000/10 = 100 CAPS

4. What is my CAPS rate during the Sustain Load stage if my call duration is 100 seconds:

CAPS = 1000/100 = 10 CAPS

5. Can I reach 1000 Ports at 20 CAPS if my call duration is 20 seconds?

Ports = CAPS * Call Duration = 20 * 20 = 400 Ports

Answer: No. The max Ports at this setup is 400.

 

Related articles

Comments

2 comments

Date Votes
  • Gokhan Akdemir

    Hi Valery,

    Could you please explain calculation for Voice Pulse campaign?

    If we have 4 concurrent ports ,frequency is 60 mins, Max CAPS 20.

    How many call will be performed by Cyara with round-robin configuration for an hour?

    20/4=5 is correct calculation for each configured test case, correct?

    If we have configured 2 test cases, Cyara will be performed 10 calls for an hour.

    Regards,

    Gokhan Akdemir 

     

    0
  • Valery Topilin
    • Edited

    Hi Gokhan,

    The math above is applicable for Load Testing campaigns, because Cruncher allows 3 parameters: CAPS, Ramp Up Time, Ports.

    Pulse campaigns are different, they run on the schedule and each cycle Pulse campaigns places as many calls as many test cases added to the campaign (or DataDriven scenarios attached).

    Example1:

    Campaign 1 scheduled to run every 15 minutes, with concurrency 1 port, with 5 test cases added. Each of the test cases have about 2 minutes duration.

    • 12:00am Cyara starts dialing the 1st call with concurrency 1.
    • 12:02am 1st call is over and second starts
    • 12:10am the last call is completed
    • 12:15am the next cycle starts

    Example2:

    Campaign2 is scheduled to run every 20 minutes, with CAPS 20, and 4 ports. Campaign has the same 5 test cases attached with 2 minutes duration avg.

    • 12:00am Cyara starts all 4 test cases at the same time, because number of test cases is less than CAPS
    • 12:02am 4 test cases are completed. Cyara places the last 5th call to complete a cycle and test all 5 test cases attached to the campaign
    • 12:04am cycle ends
    • 12:20am the next cycle starts

    As you can see in both scenarios Cyara places a many calls as needed to test all of the test cases or scenarios attached to the campaign. When a cycle ends, Cyara waits for the next start time to test all of these test cases again.

     

    0

Please sign in to leave a comment.