Help on improving performance on multiuser Protégé OWL

[Rune Stilling]

Hi there

I have set up a Protégé server (3.4 beta, build 504) serving an ontologi containing about 25000 concepts. My problem is that the client runs extremely slow when showing details on instances. This is the case both for the individuals, instances and instancetree tabs. When I clik an instance it takes at least 10 seconds for the client to show the instance's form. This is also the case when the instance list contains only a few hundred instances (still 25k instances in total in the whole ontology).

Are there any ways to improve performance drastically or is this to be expected?

Regards
Rune

[Tania Tudorache]

Hi Rune,

I recommend that you use the InstancesTab, rather than the
OWLIndividualsTab in client-server, because the latter one still has
some performance problems.

If you experience delays after clicking on an instance, is because the
form generation takes a long time. This can also happen if you use
composed browser slots for the instances that are shown on an instance
form. One thing that you can try is to customize the class form and to
remove all the properties that you don't want to see on the instance form.

We can certainly improve the performance of form generation. If you have
an example ontology with instances and complex forms, please send it to
us. It would help a lot with the debugging.

Thanks,
Tania



Rune Stilling wrote:

> Hi there
>
> I have set up a Protégé server (3.4 beta, build 504) serving an ontologi
> containing about 25000 concepts. My problem is that the client runs
> extremely slow when showing details on instances. This is the case both for
> the individuals, instances and instancetree tabs. When I clik an instance it
> takes at least 10 seconds for the client to show the instance's form. This
> is also the case when the instance list contains only a few hundred
> instances (still 25k instances in total in the whole ontology).
>
> Are there any ways to improve performance drastically or is this to be
> expected?
>
> Regards
> Rune
>  

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 

[Rune Stilling]

Hi Tania

I do use the InstancesTab and I only have around 10 attributes in average on my forms. Still it takes more than 10 seconds to generate the instances form working in multiuser mode, which seems kind of strange since there's shouldn't be that much data passing back and forth from the client to the server.

When I run on a local server the system is a lot faster.

I'll send you the ontology by mail.

Regards
Rune

Tania Tudorache wrote:

Hi Rune,

I recommend that you use the InstancesTab, rather than the
OWLIndividualsTab in client-server, because the latter one still has
some performance problems.

If you experience delays after clicking on an instance, is because the
form generation takes a long time. This can also happen if you use
composed browser slots for the instances that are shown on an instance
form. One thing that you can try is to customize the class form and to
remove all the properties that you don't want to see on the instance form.

We can certainly improve the performance of form generation. If you have
an example ontology with instances and complex forms, please send it to
us. It would help a lot with the debugging.

Thanks,
Tania



Rune Stilling wrote:
> Hi there
>
> I have set up a Protégé server (3.4 beta, build 504) serving an ontologi
> containing about 25000 concepts. My problem is that the client runs
> extremely slow when showing details on instances. This is the case both for
> the individuals, instances and instancetree tabs. When I clik an instance it
> takes at least 10 seconds for the client to show the instance's form. This
> is also the case when the instance list contains only a few hundred
> instances (still 25k instances in total in the whole ontology).
>
> Are there any ways to improve performance drastically or is this to be
> expected?
>
> Regards
> Rune
>  

_______________________________________________
protege-owl mailing list
[e-mail]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 

[Tania Tudorache]

Hi Rune,

Thanks a lot for sending the ontology.

Form generation in OWL is more complicated than in frames because of the
of the open world assumption. So, just to compute what form for which
properties to be shown is pretty expensive (the algorithm looks at the
domain and ranges of properties, at restrictions, inherited
restrictions, other possibly relevant properties, etc.). In a
client-server setting, this is more expensive because each call to the
server has a penalty.

The initial computation of the form of a class could be slower, but
after that the forms should be cached and the display should be faster.
I did not optimized that part of the code yet, because we did not have
complaints about this so far, but now, it seems that the time has come
to look at it :)

Thanks,
Tania


Rune Stilling wrote:

> Hi Tania
>
> I do use the InstancesTab and I only have around 10 attributes in average on
> my forms. Still it takes more than 10 seconds to generate the instances form
> working in multiuser mode, which seems kind of strange since there's
> shouldn't be that much data passing back and forth from the client to the
> server.
>
> When I run on a local server the system is a lot faster.
>
> I'll send you the ontology by mail.
>
> Regards
> Rune
>
>
> Tania Tudorache wrote:
>  
>> Hi Rune,
>>
>> I recommend that you use the InstancesTab, rather than the
>> OWLIndividualsTab in client-server, because the latter one still has
>> some performance problems.
>>
>> If you experience delays after clicking on an instance, is because the
>> form generation takes a long time. This can also happen if you use
>> composed browser slots for the instances that are shown on an instance
>> form. One thing that you can try is to customize the class form and to
>> remove all the properties that you don't want to see on the instance form.
>>
>> We can certainly improve the performance of form generation. If you have
>> an example ontology with instances and complex forms, please send it to
>> us. It would help a lot with the debugging.
>>
>> Thanks,
>> Tania
>>
>>
>>
>> Rune Stilling wrote:
>>    
>>> Hi there
>>>
>>> I have set up a Protégé server (3.4 beta, build 504) serving an ontologi
>>> containing about 25000 concepts. My problem is that the client runs
>>> extremely slow when showing details on instances. This is the case both
>>> for
>>> the individuals, instances and instancetree tabs. When I clik an instance
>>> it
>>> takes at least 10 seconds for the client to show the instance's form.
>>> This
>>> is also the case when the instance list contains only a few hundred
>>> instances (still 25k instances in total in the whole ontology).
>>>
>>> Are there any ways to improve performance drastically or is this to be
>>> expected?
>>>
>>> Regards
>>> Rune
>>>  
>>>      
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl@...
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03 
>>
>>
>>    
>
>  

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 

[Rune Stilling]

Hi Tania

You wrote:

Tania Tudorache wrote:

The initial computation of the form of a class could be slower, but
after that the forms should be cached and the display should be faster.
I did not optimized that part of the code yet, because we did not have
complaints about this so far, but now, it seems that the time has come
to look at it :)

I'm a bit curious as to how big ontologies other people are working with using client/server mode.

I have tried to reduce the size of my ontology so it now contains less than 5000 instances and classes, no cardiniality constraints, etc. Still showing instances takes more than 10 seconds, which makes it hard to work with. So - Maybe there's something that I'm not aware of slowing performance drastically? I can not imagine anybody else using Protégé in c/s mode with 5000+ ontology not "complaining" about this issue.

BTW it doesn't really matter weather I use file og database mode.

Regards
Rune

[Rune Stilling]

I have uploaded a screen cast of the slow Protégé client. Especially showing instances is very slow - look at the end of the movie for this.

http://screencast.com/t/x7ldnHNOz4z

In the bottom of the screen it's possible to monitor CPU and network usage.

I'm running newest 505 edition.

\Rune