SAP Knowledge Base Article - Preview

3715425 - Parameter enq/io/max_threads: Understanding ENSA2 threading, performance expectations, and tuning limits

Symptom

Some of the below questions arise:

  • Why does increasing enq/io/max_threads not help?

  • Why are all worker threads busy?

  • Is ENSA2 slower than ENSA1?

  • What is the correct value for enq/io/max_threads?

One or more of the following are observed after migrating to ENSA2 or adjusting enq/io/max_threads:

  • Increased lock response time (for example >1 ms per lock request)

  • All enqueue worker threads appearing busy

  • Slower enqueue performance compared to ENSA1

  • Performance degradation when increasing enq/io/max_threads (e.g. 32 → 64)

  • Confusion about why increasing threads does not improve performance


Read more...

Environment

  • SAP NetWeaver
  • SAP NetWeaver Application Server for SAP S/4HANA
  • ABAP PLATFORM - Application Server ABAP
  • Operating System independent
  • Database independent
  • Standalone Enqueue Server 2 (ENSA2)
  • Parameter enq/io/max_threads 

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

enq/io/max_threads; ENSA2 lock performance , KBA , BC-CST-EQ , Enqueue , BC-CST , Client/Server Technology , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.