-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.13
-
Component/s: None
-
Labels:None
-
Sprint:DEV-2013/08/08
Currently the msa modification process occurs the following way:
1) GUI detects modification -> 2) GUI addresses to the shared msa object ->
3) msa object modifies msa entity in database (typically that entity is altered partially) -> 4) msa object downloads all the msa entity from db -> 5) msa object emit signal to GUI for update with downloaded msa
The described scheme makes performance to suffer on the 4th step where huge alignment might be downloaded from database regardless of the actual modifications. Partial update from db would be rather cheaper in this case.
So the task is to allow partial msa update from db on modifications.
- blocks
-
UGENE-1867 Fix lag on removing a region in a large msa
- Closed