Closed Bug 144337 Opened 22 years ago Closed 22 years ago

Can we short-circuit QuickDraw's implicit LockPortBits()

Categories

(SeaMonkey :: UI Design, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0

People

(Reporter: mozilla, Assigned: mozilla)

References

()

Details

(Keywords: perf, Whiteboard: [adt2 RTM])

Attachments

(1 file)

According to TechNote 2051, on Mac OS X we should be able to short-circuit
QuickDraw's implicit LockPortBits() on every QD call by stratetic usage of
::LockPortBits() and ::UnlockPortBits().

I'll attached a test patch momentarily.

Pink, care to take a gander?  In a quick jury-rigged tes, I see a 8% speedup
when forcing the entire content area to re-draw on a semi-complex HTML page
(using MacSurfer, and using the HOME/END keys to show the top/bottom).
Status: NEW → ASSIGNED
can you test this on the cowtools page-load tests and see what kind of perf
improvment it gives us there?
Keywords: nsbeta1, perf
cowtools seems to average things out much more, indicating a couple of
percentage point improvements.

Anyway, let's try this out on the trunk.  Reviews?
Comment on attachment 83457 [details] [diff] [review]
Patch to bracket our drawing rtns w/LockPortBits & UnlockPortBits

r=sdagley
Attachment #83457 - Flags: review+
Comment on attachment 83457 [details] [diff] [review]
Patch to bracket our drawing rtns w/LockPortBits & UnlockPortBits

sr=ben@netscape.com
Attachment #83457 - Flags: superreview+
Keywords: mozilla1.0
Target Milestone: --- → mozilla1.0
Checked into trunk, nominating from Moz1.0 branch
Nominating for adt1.0.1 as part of Cathleen's request during ADT meeting.

PAW - Can you find someone to verify this on the trunk, and check around for any
possible regressions, so we can take it in as early as possible?
Blocks: 143047
Keywords: adt1.0.1
Whiteboard: [adt2 RTM]
Keywords: verifyme
qa --> petersen
QA Contact: paw → petersen
Chris, could you verify this fix on the trunk.

I have today's OS X trunk build. What's the best way to verify this ?
page-loader tests?
this has been checked into the trunk, so i am resolving this as fixed. [Note: it
has been nominated for the 1.0 branch with adt1.0.1 and mozilla1.0.1 keywords].
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Spend time loading top 150 sites in the OS X trunk build (2002-06-04-08). No
problems found. Marking verified.
Status: RESOLVED → VERIFIED
adt1.0.1+ (on ADT's behalf) approval for checkin to the 1.0 branch, pending
Driver's approval. pls check this in asap, then add the keyword "fixed1.0.1".
Keywords: adt1.0.1adt1.0.1+
please checkin to the 1.0.1 branch. once there remove the "mozilla1.0.1+"
keyword and add the "fixed1.0.1" keyword.
Attachment #83457 - Flags: approval+
Fixed on Moz-1.0 branch.
So did this have any measurable performance impact?
chris - can you pls verify this on the branch, then mark it as "verified1.0.1"?
thanks!
Ran same page load tests in branch build (2002-07-16-05) with no regressions
found.  Adding verified1.0.1 keyword.
Keywords: verifymeverified1.0.1
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: