I've been getting warnings about the blast.sequence table growing large, and on looking at the table definitions, it seems like this is because records are never deleted when the blast database the record refers to is also deleted.
Right now this one table id around 935 MB. I did some basic tests and it looks like queries on this table may take a significant amount of time to return results.
I think the only reason we have this is for displaying the subject sequence in the results page. This functionality should be reproducible either using the included BLAST+ tools.
I've been getting warnings about the blast.sequence table growing large, and on looking at the table definitions, it seems like this is because records are never deleted when the blast database the record refers to is also deleted.
Right now this one table id around 935 MB. I did some basic tests and it looks like queries on this table may take a significant amount of time to return results.
I think the only reason we have this is for displaying the subject sequence in the results page. This functionality should be reproducible either using the included BLAST+ tools.