PrF UG projects project metrics - Revision history

RichMorin at 01:35, November 14, 2008

2008-11-14T01:35:26Z

RichMorin at 19:55, October 25, 2008

2008-10-25T19:55:32Z

RichMorin at 21:01, October 21, 2008

2008-10-21T21:01:26Z

RichMorin at 21:01, October 21, 2008

2008-10-21T21:01:08Z

RichMorin at 20:58, October 21, 2008

2008-10-21T20:58:45Z

RichMorin at 19:31, October 16, 2008

2008-10-16T19:31:50Z

RichMorin at 19:31, October 16, 2008

2008-10-16T19:31:07Z

RichMorin: Automated import of articles

2008-10-09T09:06:54Z

Automated import of articles

New page

__NOTOC__
== Project Metrics ==

{{PrF_UG_TOC_projects}}<div id='prf_ug'>

<i>Project metrics</i> 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:

<ol class='a'>
<li><p>
Select <b>Project | Metrics</b>.
</p>
</ol>

<div>[[Image:PrF_UG_projects_metrics.png|projects_metrics]]</div>

=== Scalability and Tuning ===

{{#var:PrF}} 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
[[PrF_UG_|Scalability and Tuning in Protege]].

</div>

@@ Line 2: / Line 2: @@
 == Project Metrics ==
-{{PrF_UG_TOC_projects}}<div id='prf_ug'>
+<noinclude>{{PrF_UG_TOC_projects}}<div id='prf_ug'></noinclude>
 <i>Project metrics</i> provide information
@@ Line 34: / Line 34: @@
-</div>
+<noinclude></div></noinclude>

@@ Line 12: / Line 12: @@
 To view project metrics, select <b>Project | Metrics</b>:
-<div>[[Image:PrF_UG_projects_metrics.png|projects_metrics]]</div>
+<div>[[Image:PrF_UG_projects_metrics.png|frame|none|
 === Scalability and Tuning ===

@@ Line 31: / Line 31: @@
 the most important thing to tune is the heap size.
 For more information, see [[Scalability and Tuning]].
 </div>

@@ Line 10: / Line 10: @@
 === Viewing Project Metrics ===
-To view project metrics:
+To view project metrics, select <b>Project | Metrics</b>:
 <div>[[Image:PrF_UG_projects_metrics.png|projects_metrics]]</div>

@@ Line 4: / Line 4: @@
 {{PrF_UG_TOC_projects}}<div id='prf_ug'>
-<i>Project metrics</i> provide information about the number of frames in the current project.
+<i>Project metrics</i> provide information
 This information can be useful in analyzing performance issues.
@@ Line 22: / Line 23: @@
 {{#var:PrF}} has successfully handled "simulated" knowledge bases
-(generated by a program)
+(generated by a program) as large as 5M frames (classes &amp; instances).
-as large as 5M frames (classes &amp;
+Actual knowledge bases as large as 100K frames give acceptable UI performance
-instances).
+if supported by the database backend.
-For file-based projects,
+For file-based projects, the primary impact of increasing the number of frames
-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).
+is that the project takes longer to load
-For database projects,
+(load time is roughly proportional to the number of frames).
-slow operations include expanding a class with a lot of direct subclasses and displaying the instances for a class with many instances.
+For database projects, slow operations include expanding a class
 Aside from limiting the size of the knowledge base,
 the most important thing to tune is the heap size.
 For more information,
-see
+see [[PrF_UG_|Scalability and Tuning in Protege]].
 </div>