Created attachment 452889 [details] [diff] [review] Patch v. 1.0 From the discussion in Bug 515549, let's do two--possibly three--things to speed up Page Info's media. 1. Lower the timeouts to the minimum of 10ms 2. Increase the number of elements processed at once 3. (Optional) Replace timeouts with postMessage as described here: http://dbaron.org/log/20100309-faster-timeouts This patch does the first two, and it can do the third if needed. http://commons.wikimedia.org/wiki/Category:Crater_Lake is a decent example of speed testing if you run "View Image Info" on the last image.
We need longer testcases. Page Info (trunk) has finished with every page I've tried so far before I could even click on the Media tab.
Created attachment 452905 [details] [diff] [review] Patch v. 1.1 Setting to 500 elements per loop.
Comment on attachment 452905 [details] [diff] [review] Patch v. 1.1 r=db48x
Attachment #452905 - Flags: review?(db48x) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a6
Version: unspecified → Trunk
Target Milestone: Firefox 3.7a6 → Firefox 3.7a5
Comment on attachment 452905 [details] [diff] [review] Patch v. 1.1 From bug 579717 this appears to fix hangs and performance problems on Mac OSX--more than it does on Windows. I propose that we port the change to 1.9.2. I will quickly make sure that the patch doesn't conflict with anything, but it shouldn't touch code that's 2.0-branch specific.
Attachment #452905 - Flags: approval18.104.22.168?
Comment on attachment 452905 [details] [diff] [review] Patch v. 1.1 Please renominate for branch landing once you've confirmed that it compiles on that branch, preferably with tryserver builds and test runs! :)
Attachment #452905 - Flags: approval22.214.171.124? → approval126.96.36.199-
Comment on attachment 452905 [details] [diff] [review] Patch v. 1.1 This works on 1.9.2 like it does on Trunk. The patch doesn't need any branch-specific changes.
Attachment #452905 - Flags: approval188.8.131.52- → approval184.108.40.206?
Comment on attachment 452905 [details] [diff] [review] Patch v. 1.1 a=beltzner for mozilla-1.9.2, simple safe perf improvement for non-critical code path
Attachment #452905 - Flags: approval220.127.116.11? → approval18.104.22.168+
This needs check-in on the 1.9.2 branch.
Can the same type of fix be applied for bug 513092?
(In reply to comment #11) > Can the same type of fix be applied for bug 513092? It's all a question of the code that populates that list. Either the code is using timeouts or it's waiting on something else. If it is the former, then yes, this same philosophy can be applied, but if it is the latter, I'm not sure. Since I don't know that code or what would be causing it, I couldn't say, but someone like Dao or Gavin would have better answers.
status1.9.2: --- → .9-fixed
Whiteboard: [c-n 1.9.2]
You need to log in before you can comment on or make changes to this bug.