[meta] Need to instrument source code for performance measurements

RESOLVED FIXED in mozilla1.2alpha

Status

P3
normal
RESOLVED FIXED
19 years ago
14 years ago

People

(Reporter: bsharma, Assigned: cathleennscp)

Tracking

({meta, perf})

Trunk
mozilla1.2alpha
x86
Windows NT
meta, perf
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
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.

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M13

Comment 1

19 years ago
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.

Comment 2

19 years ago
Did we decide when we were going to do this? M13 and M14 seem a little soon.

Updated

19 years ago
QA Contact: nobody → bsharma
Whiteboard: [PERF]

Updated

19 years ago
Blocks: 11349

Comment 3

19 years ago
We need this ASAP.  We need to be able to measure performance for beta.  And
would like to start ASAP please.

Updated

19 years ago
Severity: normal → blocker
Summary: [PERFORMANCE] Need to instrument source code for performance measurements → [BETA1]Need to instrument source code for performance measurements

Comment 4

19 years ago
Putting on Blocker [BETA1]

Comment 5

19 years ago
you can retarget to whenever. dp was beating me with a stick, making me triage
my bugs.

Updated

19 years ago
Keywords: perf

Comment 6

19 years ago
Bulk add of "perf" to new keyword field.  This will replace the [PERF] we were
using in the Status Summary field.

Updated

19 years ago
Target Milestone: M13 → M14

Updated

19 years ago
Blocks: 24206

Comment 7

19 years ago
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]

Comment 8

19 years ago
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]

Comment 9

19 years ago
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.

Updated

19 years ago
Whiteboard: could do by 2/18 if necessary → [PDT-] could do by 2/18 if necessary

Updated

19 years ago
Whiteboard: [PDT-] could do by 2/18 if necessary → [PDT-]

Updated

19 years ago
Target Milestone: M14 → M15

Comment 11

19 years ago
Moving non-essential, non-beta2 and performance-related bugs to M17.
Target Milestone: M15 → M17

Comment 12

19 years ago
post-beta2
Target Milestone: M17 → M18

Updated

19 years ago
No longer blocks: 24206

Comment 13

19 years ago
Putting on nsbeta3 radar.  QA need this for perf testing.
Keywords: nsbeta3
Whiteboard: [PDT-]

Comment 14

19 years ago
Removing nsbeta3 keyword. Performance has taken a backseat to footprint.
Keywords: nsbeta3

Updated

18 years ago
Assignee: warren → cathleen
Status: ASSIGNED → NEW
Target Milestone: M18 → ---

Comment 15

18 years ago
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

Updated

17 years ago
Blocks: 104166
(Assignee)

Updated

17 years ago
Severity: critical → normal
Summary: Need to instrument source code for performance measurements → [meta] Need to instrument source code for performance measurements

Comment 17

17 years ago
I think its time to close that one now.

/jc
(Assignee)

Updated

17 years ago
Target Milestone: --- → mozilla1.2

Comment 18

15 years ago
Done Closed
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.