Test results

System configuration:

  • Intel Core i7 CPU @ 2.80 GHz
  • 8.00 GB RAM
  • Microsoft windows 7 professional, 64 bit system
  • Ephesoft version 3.1.0.0
  • Apache Tomcat 6.0.26
  • My SQL 5.5

Case 1: Following cases show the response time it takes for n users over a period of 10 seconds.

Open Batch List

  • Data:
Users Time(ms)
100 303
500 12895
  • Chart:

Statictics 3034 openbatchlist ramp10sec.gif

Open RV screen

  • Data:
Users Time(ms)

10

1543

50

1939

100

8123

500

46760

  • Chart:

Statictics 3034 openrvscreen ramp10sec.gif

·

Move to next batch

  • Data:
Users Time(ms)

10

1075

50

2225

100

6901

500

42324

  • Chart:

Statictics 3034 movetonextbatch ramp10sec.gif

Change document type

  • Data:
Users Time(ms)

10

741

50

1253

100

4757

500

16753

  • Chart:

Statictics 3034 changedocumenttype ramp10sec.gif

Open 10 page batch

  • Data:
Users Time(ms)

10

1847

50

2222

100

8510

500

71382

  • Chart:

Statictics 3034 open10pagebatch ramp10sec.gif

Open 100 page batch

  • Data:
Users Time(ms)

10

1826

50

3260

100

10028

500

91117

·

    • Chart:

Statictics 3034 open100pagebatch ramp10sec.gif

Comparisons

  • Open batch list vs Open RV screen
  • Chart:

Statictics 3034 openbatchlistvsopenrvscreen ramp10sec.gif
 

  • Open 10 page batch vs 100 page batch
  • Chart:

Statictics 3034 open10pagebatchvsopen100pagebatch ramp10sec.gif
 

  • Response time for 500 users:
  • Chart:

Statictics 3034 responsetimefor500users ramp10sec.gif

Case 2: Following cases show the response time it takes for n users doing the action simultaneously.

Open Batch List

  • Data:
Users Time(ms)

10

801

50

2607

100

5031

500

25028

    • Chart:

Statictics 3034 openbatchlist ramp0sec.gif

Open RV screen

  • Data:
Users Time(ms)

10

2290

50

8663

100

17672

500

71472

  • Chart:

Statictics 3034 openrvscreen ramp0sec.gif

Move to next batch

  • Data:
Users Time(ms)

10

2055

50

9239

100

16416

500

52435

    • Chart:

Statictics 3034 movetonextbatch ramp0sec.gif

Change document type

  • Data:
Users Time(ms)

10

1817

50

6530

100

9616

500

21592

  • Chart:

Statictics 3034 changedocumenttype ramp0sec.gif

Open 10 page batch

  • Data:
Users Time(ms)

10

2785

50

9376

100

17957

500

88229

  • Chart:

Statictics 3034 open10pagebatch ramp0sec.gif

Open 100 page batch

  • Data:
Users Time(ms)

10

2617

50

10199

100

20248

500

107710

  • Chart:

Statictics 3034 open100pagebatch ramp0sec.gif

Comparisons

  • 10 page vs 100 page batch
  • Chart:

Statictics 3034 open10pagebatchvsopen100pagebatch ramp0sec.gif
 

  • Open Batch List vs Open RV screen
  • Chart:

Statictics 3034 openbatchlistvsopenrvscreen ramp0sec.gif
 

  • Response time for 500 users:
  • Chart:

Statictics 3034 responsetimefor500users ramp0sec.gif

Web Services Load Testing:

Terms used in load testing of Web Services

1. Ramp up – The ramp-up period tells how long to take to “ramp-up” to the full number of threads chosen. If 10 threads are used, and the ramp-up period is 100 seconds, then it will take 100 seconds to get all 10 threads up and running. Each thread will start 10 (100/10) seconds after the previous thread was begun.

2. Samples– A sample mean one sampler call. One request to web service in our case.

3. Average– This value is the average time taken to receive the result. This value is a measure of performance of the web service. This means on an average ‘x’ milliseconds time is required to receive this result.

4. Median– This is a number which divides the samples into two equal halves. Half of the samples are smaller than the median, and half are larger. The Median is the same as the 50th Percentile.

5. 90% Line– (90th Percentile) is the value below which 90% of the samples fall. The remaining samples too at least as long as the value. This is a standard statistical measure.

6. Min– This is the minimum value of time required for receiving the result from web service.

7. Max– This is the maximum value of time required for receiving the result from web service.

8. Error %– This value indicated the percentage of error. If there are any requests not received properly they are counted as errors and the percentage of error occurrence against the actual calls made is displayed in this value.

9. Throughput– This is calculated as requests/unit of time. The time is calculated from the start of the first sample to the end of the last sample. This includes any intervals between samples, as it is supposed to represent the load on the server. The formula is: Throughput = (number of requests) / (total time).

10. Kb/sec– The throughput measured in Kilobytes per second.

The load testing results are for following four web services-

1. createSearchablePDF

2. classifyHOCR

3. createHOCRforBatchClass

4. key value extraction

The load tests are for three time delays – 0 sec, 0.5 sec & 1 sec & for user count – 50. Three rounds of load test iterations have been executed for each time delay and for each web service.

The consolidated results are mapped into the excel sheets. The first sheet contains the summary of the load test cycles The second, third & fourth sheet contain the detailed load test data for Cycle1, Cycle2 & Cycle3. Then following four sheets (fifth, sixth, seventh & eighth) contain the CPU & Memory usage graphs individually specific to each load test cycle.

Load Test Results for EPHESOFT_LICENSE_TYPE_STANDARD

System configuration:

  • Intel(R) Xeon(R) CPU X5675 @3.07 GHz
  • 8.00 GB RAM
  • Windows Server 2008 R2 Enterprise (Service Pack 1), 64 bit system
  • Ephesoft version 3.1.0.0
  • Apache Tomcat 6.0.26
  • My SQL 5.5

To download the detailed Load Test Results, Click here.

Load Test Results for EPHESOFT_LICENSE_TYPE_HP4

System configuration:

  • Intel Core i7 CPU @ 2.80 GHz
  • 8.00 GB RAM
  • Microsoft windows 7 professional, 64 bit system
  • Ephesoft version 3.1.0.0
  • Apache Tomcat 6.0.26
  • My SQL 5.5

To download the detailed Load Test Results, Click here

Load Test Results for EPHESOFT_LICENSE_TYPE_HP16

System configuration:

  • Intel(R) Xeon(R) CPU X5675 @3.07 GHz
  • 8.00 GB RAM
  • Windows Server 2008 R2 Enterprise (Service Pack 1), 64 bit system
  • Ephesoft version 3.1.0.0
  • Apache Tomcat 6.0.26
  • My SQL 5.5

To download the detailed Load Test Results, Click here

 

Was this article helpful to you?

Engineering

Comments are closed.