Some customers may expect or anticipate that the performance of MyDSP 6.5 SP2 is equivalent to that of an OOTB Microsoft SharePoint Document Library.  Due to the fact that MyDSP must connect to additional servers, including DFS and Content Server, there is some expected overheard in the MyDSP architecture.  Therefore, the MyDSP product can be perceptibly slower in some operations in comparison to similar operations in OOTB SharePoint.  The differences in performance will often be completely dependent on the customer deployment architecture and geography.

Users of this product require a SharePoint account to access a Site and a Documentum account to access the Documentum content.  There are two Single-Sign-On approaches to handle this basic requirement:

• Session-Based SSO:  The user will be faced with a Documentum login when attempting to access a MyDSP Web Part.  The user will be logged in for the duration of the defined session.

• Seamless SSO:  The user will never be faced with a Documentum login when accessing a MyDSP Web Part.  This is a brand new unique type of feature that depends on Active Directory and is based on the use Kerberos technology.

In many cases, the performance of MyDSP with Seamless-SSO is slower than the performance of MyDSP with Session-Based SSO.  The difference can be up to 50% in some deployment environments.  The architecture of Seamless SSO requires extra setup, extra servers, and some additional authentication calls that account for the difference.

If the customer logs a case with slow Seamless-SSO performance, the recommendation is to try Session-Based SSO.  There are not any sizing guidelines, performance metrics, or recommended best practices documentation or tips designed to help improve performance.

Engineering and Performance Engineering are consistently working to improve performance of the product with every release.