Project

General

Profile

Bug #2613

improve performance of ScreenBitmap.canDraw (and of its callers)

Added by Constantin Asofiei almost 11 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
FWD - Performance and Scalability Improvements
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to User Interface - Feature #3246: reduce the amount of data being sent to the client-side when an UI attribute is being changed Closed

History

#1 Updated by Constantin Asofiei almost 11 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 over 10 years ago

  • Target version changed from Milestone 12 to Milestone 17

#3 Updated by Greg Shah over 9 years ago

  • Target version changed from Milestone 17 to Performance and Scalability Improvements

#4 Updated by Greg Shah over 8 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

Also available in: Atom PDF