PrF UG projects project metrics

From Protege Wiki
Jump to: navigation, search

Project Metrics

Protege-Frames User's Guide
Creating a Project
Opening a Project
Importing a Project
Saving a Project
Converting a Project's Type
Exporting a Project
Renaming a Project
Setting Preferences
Archiving a Project
Reverting to an Archived Project
Including a Project
Activating an Included Project
Removing an Included Project
Merging an Included Project
Configuring a Project
Project Metrics
Using Undo
Glossary, Editing Help

Project metrics provide information about the number of frames in the current project. This information can be useful in analyzing performance issues.

Viewing Project Metrics

To view project metrics, select Project | Metrics:

Metrics dialog

Scalability and Tuning

Protege-Frames has successfully handled "simulated" knowledge bases (generated by a program) as large as 5M frames (classes & instances). Actual knowledge bases as large as 100K frames give acceptable UI performance if supported by the database backend.

For file-based projects, the primary impact of increasing the number of frames is that the project takes longer to load (load time is roughly proportional to the number of frames). For database projects, slow operations include expanding a class with a lot of direct subclasses and displaying the instances for a class with many instances.

Aside from limiting the size of the knowledge base, the most important thing to tune is the heap size. For more information, see Scalability and Tuning.