Skip to main content
Version: 3

Benchmarking

Adeptia conducts extensive performance testing with each release to ensure improving and better performance of its product. Some performance benchmarks are provided here for reference:

Test A - Large Number of Small EDI Files​

System Configuration

  • Cluster = 2 nodes (Kernel + WebRunner)
  • Processor = Intel Xeon CPU E5-2686 2.30GHz
  • Number Of Cores = 4
  • Total RAM = 16GB
  • OS = Windows Server 2012 R2 64-bit
  • Backend / Log Database - AWS SQL RDS
  • Kernel = 8GB

Result - All tests ran successfully

ScenarioFile Size x # of FilesTotal TimeThroughput
Inbound

File Type – EDI 4010 Orders

Mapping – Medium Complex

# of ST = 1
2KB x 300013m4 files/sec
Inbound

File Type – EDI 4010 Orders

Mapping – Medium Complex

# of ST = 1
2KB x 600026m4 files/sec
Inbound

File Type – EDI 4010 Orders

Mapping – Medium Complex

# of ST = 1
2KB x 20,0001h 46m3.14 files/sec
Inbound

File Type – EDI 4010 Orders

Mapping – Medium Complex

# of ST = 44
37KB x 10001h 12m4 files/sec
Outbound EDI from IDOC

File Type – EDI 4010 Invoice

Mapping – Medium Complex
11KB x 300012m 08s4.12 files/sec

Test B - Large Sized EDI Files​

System Configuration

  • Single node (no cluster)
  • Processor = Intel Xeon CPU E5-2686 2.30GHz
  • Number Of Cores = 4
  • Total RAM = 16GB
  • OS = Windows Server 2012 R2 64-bit
  • Backend / Log Database - AWS Oracle RDS
  • Kernel = 8GB

Result: All tests ran successfully

ScenarioFile Size x # of FilesMax CPU %Max RAM %Max. Kernel HeapTotal Time
Inbound

File Type – EDI 4010

ISA : 1

GS : 1

Transaction Set : 5000

~ 25-35 segments in each transaction set
2.79MB x 142%38%1.1GB34s
Inbound

File Type – EDI 4010

ISA : 1

GS : 13

Transaction Set : 1 ST in each GS

~ 140000 segments in each transaction set
40.1MB x 188%46%2.3GB5m 22s
Inbound

File Type – EDI 4010

ISA : 1

GS : 1

Transaction Set : 10000

~ 50-103 segments in each Transaction set
13.6MB x 172%43%2.2GB1m 31s

Test C - Large File Processing with Large Data Ingestion​

System Configuration

  • Single node (no cluster)
  • Processor = Intel Xeon CPU E5-2686 2.30GHz
  • Number Of Cores = 4
  • Total RAM = 16GB
  • OS = Windows Server 2012 R2 64-bit
  • Backend / Log Database - AWS Oracle RDS
  • Kernel = 8GB

Result: All test ran successfully

ScenarioFile Size x # of FilesNumber of Records per fileMax CPU %Max RAM %Time
File Type – XML

Mapping – Simple 1-to-1

# of Files = 1
25GB x 169689527%34%23m 48s
50GB x 1139369027%34%47m 30s
200GB x 1557476027%34%3h 10m
500GB x 11393690027%34%7h 52m
File Type – XML

Mapping – Simple 1-to-1

# of Files = 50 parallel
25GB x 50696895100%37%10h 7m (total)

8h 51m (avg/file)
50GB x 501393690100%37%19h 45m (total)

17h 13m (avg/file)
File Type – XML

Mapping – Complex (Functions used: Math, String, DB Look, If Condition)

# of Files = 1
25GB x 169689529%36%33m 30s
50GB x 1139369029%36%1h 7m
200GB x 1557476029%36%4h 27m
500GB x 11393690029%36%11h 13m
File Type – XML

Mapping – Complex

# of Files = 50 parallel
25GB x 50696895100%39%9h 59m (total)

8h 22m (avg/file)
50GB x 501393690100%39%20h 2m (total)

15h 53m (avg/file)
File Type – TEXT

Mapping – Simple 1-to-1

# of Files = 1
25GB x 169689545%36%6h 26m
50GB x 1139369045%36%12h 40m
200GB x 1557476045%36%51h 30m

Test D - UI Load Testing with Concurrent Users​

System Configuration

  • Single node (no cluster)
  • Processor = Intel Xeon CPU E5-2686 2.30GHz
  • Number Of Cores = 4
  • Total RAM = 16GB
  • OS = Linux 64-bit
  • Backend / Log Database - AWS Oracle RDS
  • Kernel = 8GB
  • WebRunner = 4GB
  • Tool used = JMeter

Result: All tests ran successfully

ScenarioHome PageDashboardNetworkPartnersTransactionsMax CPU %Max RAM %
# of Partners and Transactions in Back-end DB = 1138

# of Concurrent Users = 25

# of Loops (iterations) = 50
4.2s1.1s0.8s0.4s0.6s53%64%
# of Partners and Transactions in Back-end DB = 1638

# of Concurrent Users = 25

# of Loops (iterations) = 50
4.3s1.0s0.9s0.3s0.4s49%59%
# of Partners and Transactions in Back-end DB = 2200

# of Concurrent Users = 25

# of Loops (iterations) = 50
2.3sOverview page : 4.3s9.0s0.7s2.7s64%59%
Transaction page: 0.4s
Trigger page: 0.5s

Test E - Advanced Positional File​

System Configuration

  • Single node (no cluster)
  • Processor = Intel Xeon CPU E5-2686 2.30GHz
  • Number Of Cores = 4
  • Total RAM =64GB
  • OS = Windows Server 2012 R2 64-bit
  • Backend / Log Database - AWS Oracle RDS
  • Kernel = 20GB (minimum), 40GB (maximum)

Result - All tests ran successfully

ScenarioNumber of Records per fileFile Size x # of FilesTotal Time
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
3 million234 Mb x 145m 39s
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
5 million391 Mb x 11h 19m 31s
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
10 million782 Mb x 12h 31m 49s
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
10 million782 Mb x 32h 13m 4s
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
10 million782 Mb x 52h 12m 37s
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
10 million782 Mb x 102h 42m 45s
File Type – Text to Advanced Positional

Mapping – Simple 1-to-1
10 million782 Mb x 153h 56m 36s

Test F - API Load Testing Results​

The API load testing results are documented in Test_Result_WebService_LoadTesting_V3.5.pdf.

Test G - Schema​

Sl. No.Test Case DescriptionData Set
(File
Size)
Execution Time
1To test processing of simple Excel file (xls) through File Event, File Source and File target





Performance_Process_flow_Excel
100 MB1 min 28 sec

Kernel CPU: 25%
WebRunner CPU: 0.00%

Kernel Mem: 5.5GB
WebRunner Mem: 854MB
2To test processing of simple Positional file through File Event, File Source and File target 




Performance_Process_flow_Positional
100 MB59 sec

Kernel CPU: 27%
WebRunner CPU: 0.00%

Kernel Mem: 7.21GB
WebRunner Mem: 855MB
3To test processing of simple JSON file through File Event, File Source and File target 




Performance_Process_flow_JSON
100 MB25 sec

Kernel CPU: 3%
WebRunner CPU: 0.03%

Kernel Mem: 8.7GB
WebRunner Mem: 855MB
4To test processing of simple Adv Positional file through File Event, File Source and File target 




Performance_Process_flow_Adv_Positional
100 MB1 min 15 sec

Kernel CPU: 29%
WebRunner CPU: 0.00%

Kernel Mem: 8.2GB
WebRunner Mem: 830MB
5To test processing of simple Text file through File Event, File Source and File target 




Performance_Process_flow_Text
100 MB2 min 00 sec

Kernel CPU: 28.5%
WebRunner CPU: 0.00%

Kernel Mem: 8.5GB
WebRunner Mem: 855MB
6To test processing of simple Adv. Text file through File Event, File Source and File target 




Performance_Process_flow_adv_text
100 MB1 min 49 sec

Kernel CPU: 25%
WebRunner CPU: 0.00%

Kernel Mem: 8.6GB
WebRunner Mem: 856MB
7To test processing of simple xml file through File Event, File Source and File target 




Performance_Process_flow_Xml
100 MB7 sec

Kernel CPU: 19%
WebRunner CPU: 0.3%

Kernel Mem: 8.85GB
WebRunner Mem: 855MB
8To test Database Event along with Adv Database Source when the number of records to pick up are large in the table. Use one to map to write data to Adv DB target with different batch/commit size options.





Performance_Process_flow_Adv_Database
50000 records to pickup Batch size=5000

Commit Size=2500
1 min 36 sec

Kernel CPU: 19.8%
WebRunner CPU: 0.00%

Kernel Mem: 3.56GB
WebRunner Mem: 841MB
9To test Database Event along with Adv Database Source when the number of records to pick up are large in the table. Use one to map to write data to Adv DB target with different batch/commit size options.





Performance_Process_flow_Adv_Database
50000 records to pickup Batch size=5000

Commit Size=5000
1 min 40 sec

Kernel CPU: 20.2%
WebRunner CPU: 0.00%

Kernel Mem: 3.34GB
WebRunner Mem: 839MB

Test H - Miscellaneous​

Sl. No.Test Case DescriptionData Set
(File
Size)
Execution Time
1To test concurrent processing of flat files of different sizes with moderate mapping functions and one to one conversion.File Type: CSV

File Size: 1MB

Concurrent Files: 500
2 min 54 sec

Kernel CPU: 5.20%
WebRunner CPU: 0.00%

Kernel Mem: 3.33GB
WebRunner Mem: 824MB
2To test concurrent processing of flat files of different sizes with moderate mapping functions and one to one conversion.File Type: CSV

File Size: 1MB

Concurrent Files: 1000
9 min 32 sec

Kernel CPU: 5.82%
WebRunner CPU: 0.00%

Kernel Mem: 3.34GB
WebRunner Mem: 834MB
3To test concurrent processing of flat files of different sizes with moderate mapping functions and one to one conversion.File Type: CSV

File Size: 100KB

Concurrent Files: 5000
4To test processing of flat files located at File through non-streaming Mapping with pre-built Mapping functions applied (string, conditional, date, math) and generate the Target file.100MB Plain CSV Text file

Non-streaming Mapping mode
1 min 40 sec

Kernel CPU: 2.5%
WebRunner CPU: 0.00%

Kernel Mem: 3.37GB
WebRunner Mem: 836MB