bildwelt
E2E FORUM
E2E Bridge E2E Commerce

Reply To: performance metrics

E2E Forum General Discussion performance metrics Reply To: performance metrics

#789

Marcel R.
Blocked

Hi Paul,

unfortunately I cannot provide you with a standardized performance tests. The latency of Bridge services depends very much on the used Bridge components and is typically limited by calls to external systems because the Bridge is typically used for integration projects and not number crunching. However, we went to great lengths to scale integration use cases linearly. This is a very important feature because it allows you to keep your latency low for increasing load by scaling up hardware – either more CPU power or more nodes. For example, Oracle tested this behavior explicitly when we did our Oracle middle ware certification (see table below).

Another performance bottle neck might be persistent state objects when using external databases as storage. Attached you find some tests we did for this use case. More about persistent state performance can also be found here.

 

 

Memory & Latency Scaling Tests Oracle/SAP Communication

Test StepsTest Description/ProcessBehavior
Data ScalingLoad will be produced from SAP using SAP test tool (WE19). Use of scenario BPEL_SAP_Inbound – IDOC.

  1. 10 IDOCS
  2. 20 IDOCS
  3. 50 IDOCS
  4. 100 IDOCS
  5. 200 IDOCS
System stays stable, no loss of data.

 

Latency and memory scale linearly.

Runtime Scaling:

Test for the Heavy Load from BPEL to SAP bridge

Load will be produced from BPEL using scenarios

  • BPEL_SAP_Outbound – BAPI
  • BPEL_SAP_Outbound – IDOC

 

  1. BPEL_SAP_Outbound – BAPI
    1. Conc. Threads 1, Loops 10, Delay ms 1000
    2. Conc. Threads 2, Loops 10, Delay ms 1000
    3. Conc. Threads 1, Loops 20, Delay ms 500
    4. Conc. Threads 2, Loops 20, Delay ms 500
    5. Conc. Threads 5, Loops 20, Delay ms 500
    6. Conc. Threads 10, Loops 50, Delay ms 500
    7. BPEL_SAP_Outbound – IDOC
      1. Conc. Threads 1, Loops 10, Delay ms 1000
      2. Conc. Threads 2, Loops 10, Delay ms 1000
      3. Conc. Threads 1, Loops 20, Delay ms 500
      4. Conc. Threads 2, Loops 20, Delay ms 500
      5. Conc. Threads 5, Loops 20, Delay ms 500
      6. Conc. Threads 10, Loops 50, Delay ms 500
System stays stable, no loss of data.

 

Memory scales linearly.

The tests run on a one processor PC with 4GB memory.