Template:Software:Database Limitations: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
The current backend in AmiGO
The term enrichment tool and slimmer both suffer from timeout and load issues on their current hardware. Unfortunately, at this time, they are limited in the amount of work that they can accomplish before a timeout event occurs either on the client or server. Due to these limitations, the current tool is not really designed to work on sets beyond a certain size. Unfortunately, this size is hard to pinpoint; depending on input type, size, and database warmup, the results available may be very different. If you get a timeout error, or see a phrase like "Query execution was interrupted", you have probably reached the time resource limit.
The term enrichment tool and slimmer both suffer from timeout and load issues on their current hardware. Unfortunately, at this time, they are limited in the amount of work that they can accomplish before a timeout event occurs either on the client or server. Due to these limitations, the current tool is not really designed to work on sets beyond a certain size. Unfortunately, this size is hard to pinpoint; depending on input type, size, and database warmup, the results available may be very different. If you get a timeout error, or see a phrase like "Query execution was interrupted", you have probably reached the time resource limit.



Revision as of 15:52, 28 October 2013

The term enrichment tool and slimmer both suffer from timeout and load issues on their current hardware. Unfortunately, at this time, they are limited in the amount of work that they can accomplish before a timeout event occurs either on the client or server. Due to these limitations, the current tool is not really designed to work on sets beyond a certain size. Unfortunately, this size is hard to pinpoint; depending on input type, size, and database warmup, the results available may be very different. If you get a timeout error, or see a phrase like "Query execution was interrupted", you have probably reached the time resource limit.

In the fairly near future we'll be moving to a Galaxy based workflow system that will not have these same limitations in size and time. Until then, you may wish to take a look at other available third-party tools:

 http://neurolex.org/wiki/Category:Resource:Gene_Ontology_Tools

Or look at a tool like Ontologizer:

 http://compbio.charite.de/contao/index.php/ontologizer2.html