Server Side Memory Pain

• Unsubstantiated rumor: "2M per connection!"

• What the docs say

  • 100K VM per database, smaller VM per connection
  • SET OPTION JAVA_NAMESPACE_SIZE = 4000000
    • Per database maximum, from cache
  • SET OPTION JAVA_HEAP_SIZE = 1000000
    • Per connection maximum, from cache

• Measured

  • 20M to start server, including 16M cache
  • 1.4M cache 1st connection, 124K per later connection
  • Another 9K per connection outside cache

Previous slide

Next slide

Back to first slide

View graphic version

Each connection that uses Java requires a minimum of 124K from the server cache; this isn't too bad.