Extremely large CAZy database releases is increasing the memory intensity of cazy_webscraper, making it difficult to run the tool on standard office equipment (see issue at cazomevovle).
The issue comes down to parsing the large CAZy text file (the CAZy db dump), and passing the data into a dict, which is memory intensive. This method needs to be changed, and broken up to reduce the computational load - ideally to below 8GB.
Extremely large CAZy database releases is increasing the memory intensity of
cazy_webscraper
, making it difficult to run the tool on standard office equipment (see issue atcazomevovle
).The issue comes down to parsing the large CAZy text file (the CAZy db dump), and passing the data into a dict, which is memory intensive. This method needs to be changed, and broken up to reduce the computational load - ideally to below 8GB.