Dashboard > Penrose 1.2 > ... > Penrose Server User Guide > Performance
Performance
Added by Jim Yang, last edited by Endi S. Dewata on Jul 31, 2007  (view change)
Labels: 
(None)


Introduction

Compared to a regular LDAP server, especially the native ones, Penrose is expected to be slower because it has to dynamically translate incoming LDAP requests into another form (e.g. SQL query), perform the operations on the data sources, then translate the results back into LDAP responses.

The actual performance of Penrose depends on several factors including:

  • Datasource performance
  • Size of data
  • Complexity of mapping configuration
  • Network latency
  • Hardware and JVM performance

There are several methods to fine-tune Penrose's performance:

  • Use simple mapping when possible
  • Limit the size of the data retrieved per operation
  • Use cache when real-time mapping is not required
  • Run Penrose and datasource in the same machine
  • Replicate the datasource into a faster system

Site running on a free Atlassian Confluence Open Source Project License granted to Safehaus. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.4 Build:#809 Jun 12, 2007) - Bug/feature request - Contact Administrators