I've been looking into various tuning properties that are available for Protege and some of these provide scope for tuning performance, which I thought might be worth exploring to if it seems that the Client / Server performance is low.
From the Advanced Client Server Tutorial for Protege Client Server
There are also some properties that control the level of instance pre-loading that the client does that may also be worth exploring.There is another setting that can be very important for performance:This option enables compression on the client-server connection. It will increase the cpu usage on the client and the server but can provide quite a significant improvement in bandwidth usage (early experiments suggest a compression factor of up to 10 to 1 and performance on the client is doubled for some large ontologies).Code: Select all
-Dserver.use.compression=true
Finally, the option:... controls the level of protection associated with transactions. The options are:Code: Select all
-Dtransaction.level=...
- NONE - which means that transactions do not even have rollback capabilities. This is not recommended.
- READ_UNCOMMITTED - which means that users can see other users changes even if the other user is in a transaction and has not committed the transaction.
- READ_COMMITTED - which means that user operations made during a transaction are not seen by other users until they are committed.
- REPEATABLE_READ - which means that the system assures a user in a transaction that data he reads will not change for the duration of the transaction.
- SERIALIZABLE - which means that transactions are serializable. This is the most stringent form of transaction processing but it is also the most expensive and the most likely to cause problems with locked databases.
Jonathan