process and load UMLS 2021AB release

[alexskr]

No description provided.

[alexskr]

NCBITAXON ontology hasn't been updated since 2020AB and needs to be fixed

[alexskr]

owlapi-wrapper run out of java heap space. Hardcoded -Xmx10240M is not enough to process NCBITAXON

[jonquet]

Hi @alexskr
@syphax-bouazzouni has created a PR to address the setting of the heap-size:
ncbo/ontologies_linked_data#130

We have another out of memory issue showing up (at 4store level) after significantly increasing the heap size at the owl-api level (10>20Gb). We would be interested to know if you run into this too with NCBITAXON.
ontoportal-lirmm/ontologies_linked_data#15 (comment)

[alexskr]

@syphax-bouazzouni PR looks great! Thank you!

@jonquet we are not running into this particular problem with 4store when processing NCBITAXON but our environment might be different from what you have. We use separate/dedicated VMs for parsing/ncbo_corn and for 4store so we don't have a memory contention issue you might be running into. Also, we use a secondary 4store instance when processing UMLS ontologies so that it doesn't have to serve life bioportal traffic.