Closed Bug 23036 Opened 25 years ago Closed 21 years ago

[meta] Need to instrument source code for performance measurements

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
mozilla1.2alpha

People

(Reporter: bsharma, Assigned: cathleennscp)

References

Details

(Keywords: meta, perf)

As per our discussion in the Performance meeting developers need to instrument the source code. Please let me know when some of the instrumentation is ready to use so that I can start designing the scripts required.
Status: NEW → ASSIGNED
Target Milestone: M13
I've started some of this, but didn't get very far. I did develop an nsIStopwatch interface/implementation that can be used for this purpose (supercedes stopwatch.h in libutil), but quickly hit problems using it in practice (e.g. appcore callbacks that were never called, etc). I plan to look at it a little more in the next few days.
Did we decide when we were going to do this? M13 and M14 seem a little soon.
QA Contact: nobody → bsharma
Whiteboard: [PERF]
Blocks: 11349
We need this ASAP. We need to be able to measure performance for beta. And would like to start ASAP please.
Severity: normal → blocker
Summary: [PERFORMANCE] Need to instrument source code for performance measurements → [BETA1]Need to instrument source code for performance measurements
Putting on Blocker [BETA1]
you can retarget to whenever. dp was beating me with a stick, making me triage my bugs.
Keywords: perf
Bulk add of "perf" to new keyword field. This will replace the [PERF] we were using in the Status Summary field.
Target Milestone: M13 → M14
Blocks: 24206
removing vestigial tags, moving leger's beta1 tag to keyword field
Keywords: beta1
Summary: [BETA1]Need to instrument source code for performance measurements → Need to instrument source code for performance measurements
Whiteboard: [PERF]
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Although this would be nice to do for beta, I don't think this is something we wouldn't ship the beta without. Erasing PDT+ designation for reassessment.
Whiteboard: [PDT+] → could do by 2/18 if necessary
FWIW, I agree with Warren.
Whiteboard: could do by 2/18 if necessary → [PDT-] could do by 2/18 if necessary
Whiteboard: [PDT-] could do by 2/18 if necessary → [PDT-]
Target Milestone: M14 → M15
Moving non-essential, non-beta2 and performance-related bugs to M17.
Target Milestone: M15 → M17
post-beta2
Target Milestone: M17 → M18
No longer blocks: 24206
Putting on nsbeta3 radar. QA need this for perf testing.
Keywords: nsbeta3
Whiteboard: [PDT-]
Removing nsbeta3 keyword. Performance has taken a backseat to footprint.
Keywords: nsbeta3
Assignee: warren → cathleen
Status: ASSIGNED → NEW
Target Milestone: M18 → ---
this sound more like a tracking bug.. maybe a topic for upcoming perf meeting to figure out exactly what we should do and who should do it. over to cathleen... removing m18
Meta, not a blocker
Severity: blocker → critical
Keywords: meta
Blocks: 104166
Severity: critical → normal
Summary: Need to instrument source code for performance measurements → [meta] Need to instrument source code for performance measurements
I think its time to close that one now. /jc
Target Milestone: --- → mozilla1.2
Done Closed
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.