Child pages
  • Performance
Skip to end of metadata
Go to start of metadata

The BSP runtime itself is relatively lean. Performance of any BSP application is very much influenced by the BSP application itself. Here are references to documents and notes that can be used to get a handle on the performance of a BSP application.
Note that the biggest drag on performance is shear rendering sizes. Specifically limit the number of columns and rows that are actively displayed in one tableView. Otherwise, the rendered HTML can quickly jump into hunderds of kilobytes. This influences the server rendering time, the transfer time of the data to the client, and definitely will make the client rendering crawl.

Weblog Series on BSP Performance

  • Compression
    Usually the number of bytes in transit is never a concern, especial in these giga days. However, it definitely pays to look at the actual traffic occasionally. This article discusses a few approaches with which the bandwidth requirements per request can be reduced dramatically.
  • Measuring Roundtrip Latency
    This Weblog will show a step-by-step example of measuring the HTTP roundtrip latency for a "Hello World" BSP page. This can be used as baseline to determine the actual latency of the network and the BSP runtime.
  • Statistic Records for Server Latency
    In a previous Weblog we looked at the HTTP roundtrip latency for a "Hello World" BSP page. However, this included a large network component (especially when working from home!), and did not reflect the true server load per request. In this Weblog we use statistic records to show quickly what is the processing time on the server for each HTTP request.
  • Determining Hotspots
    Knowing the HTTP roundtrip latency and the server execution time is fine, but still does not satisfy our curiosity. What is the server doing? What is taking so long? Typically when colleagues have performance problems with the BSP applications, we show them first what is the real latency of the BSP roundtime for a "Hello World" BSP page. Any larger number means application time. And of course now  comes the confusing question: what is the application doing? This Weblog shows how to see exactly what the application is doing at a very fine granular level.

SAP Notes


  • No labels