Scalability

Post Reply
peter van mortsel
Posts: 8
Joined: 13 Dec 2010, 12:31

Hi,

How many instances * slots can be inserted in EAM before performance issues might occure ... and if so are there ways to overcome this ... additional indexing, specific logical or hardware implementations?

Are there EAM consultants in the neighbourhood of Belgium to improve our approaches and progress?

Thx
peter.
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Peter,

The Protege platform that provides the repository and modelling platform for Essential Architecture Manager is highly scaleable. The Protege team themselves have done some research and suggest that once you exceed 100,000 instances you need to be using a database backend for the repository (the Protege Project) rather than the file-based backend that is the default for stand-alone mode in Essential.

We would suggest that once your repository starts to get large and in certainly if you are running in multi-user mode, then you should be using a database backend.

Once you are using the database backend, the platform will scale to over 1,000,000 instances - based on Protege team's research. We have a number of clients running 10,000's of instances both stand-alone with file-based repository (which needs plenty of memory!) and multi-user mode with a database backend with very good performance.
In the Protege 3.4 release (Q2 2009) introduced some enhancements to the user interface to populate instance browsers in a multi-threaded manner which was a great improvement to usability for large repositories.

Essential services are provided by EAS and their affiliates. The affiliate network is growing all the time. The nearest consultants to Belgium are currently based out of London but they would be happy to help you with making the best use of EAM. Please see the Services menu for more information and the services request form.

Jonathan
Essential Project Team
Post Reply