Bug #2613
improve performance of ScreenBitmap.canDraw (and of its callers)
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
Related issues
History
#1 Updated by Constantin Asofiei almost 9 years ago
In GUI, ScreenBitmap.canDraw
(and its callers, getVerticalFragments
and getHorizontalFragments
) are used intensively. The performance for canDraw
is poor - it iterates all registered rectangles in ScreenBitmap.bitmap
to determine if the specified point is part of it. This should be improved so that search is done faster: maintain some parallel sorted arrays by column/row, and use binary search on them?
#2 Updated by Greg Shah about 8 years ago
- Target version changed from Milestone 12 to Milestone 17
#3 Updated by Greg Shah over 7 years ago
- Target version changed from Milestone 17 to Performance and Scalability Improvements
#4 Updated by Greg Shah over 6 years ago
- Related to Feature #3246: reduce the amount of data being sent to the client-side when an UI attribute is being changed added