Configuration choices and tradeoffs covers some important
configuration and application design choices when planning a Content Manager EE Version 8 system, focusing
on the performance implications of those choices.
- ACL: Time-optimized or space-optimized?
-
- The default time-optimized ACL mode adds all possible combinations
of ACL rules, user groups, and privileges to the ICMSTCompiledACL
table, which can improve performance unless your ICMSTCompiledACL
table is huge.
- The space-optimized ACL mode adding only one combination of the
ACL and user group to the table, which might affect runtime performance
but can save space and increase performance for regular administrative
actions.
- For more information, see Changing
the ACL optimization mode
- Web clients or desktop clients?
-
- Desktop clients are typically faster than Web clients
- Web clients are typically easier to deploy and maintain
- For Web clients: Direct retrieve or mid-tier conversion?
-
- Direct retrieve is faster and more scalable
- Direct retrieve might require browser plug-ins or viewer applet
- IBM® client program or custom
client program?
-
- A custom client program can be tuned to your exact requirements
- The IBM clients already
use our latest general-purpose tuning methods
- For custom clients: Beans (non-visual, or non-visual + visual),
or Java™ or C++ OOAPI?
-
- Beans implement only the document model
- Beans support rapid application development
- OOAPIs will have the best performance
- For Java or C++ OOAPI custom
clients: Document model or custom data model?
- The document data model already includes our latest general-purpose
tuning methods
- A custom data model can be tuned to your exact requirements
- Versioning
-
- Versioning increases the library server database size
- Accessing current version is faster than accessing previous versions
- Attribute indexes
- Appropriate indexes improve performance of searches and reduce
library server resource usage
- Indexes increase library server database size, and affect store
and update times
- Resource manager asynchronous and third-party ingest/delivery
-
- Asynchronous and third-party require custom clients
- Appropriate for very large objects, such as for VideoCharger
- Library server and resource manager on the same or separate systems
- Higher scalability when on separate systems
- Single or multiple resource managers
-
- Multiple resource managers give higher total bandwidth for larger
objects
- Multiple resource managers give higher migrator parallelism
- Distributed resource managers located close to end users provide
better performance
- Number of resource manager collections
-
- Multiple collections give higher migrator parallelism (one thread
per collection)
- Server platform choice
-
- Mid-tier server
- Content Manager EE Version 8 Java OOAPI supported on AIX®, Solaris, and Windows
- Some other connectors are Windows-only
- Java conversion engine is
cross-platform
- Library server and resource manager
- Higher scalability on other operating systems than Windows
