Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / mozilla-mobile/perf-frontend-issues issues and pull requests
#106 - Tracking down leanplum (for clicking on URL bar)
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#105 - Create "how to performance test" splash page
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#104 - Use simpleperf to take start up profile using rooted phone for investigating deps/asset uncompression
Issue -
State: closed - Opened by MarcLeclair almost 5 years ago
- 1 comment
#103 - Take video side by side of Fenix from December / January vs Now (as of April)
Issue -
State: closed - Opened by MarcLeclair almost 5 years ago
- 3 comments
#102 - FNPRMS is missing results from 4/21-4/23, 4/27
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 10 comments
#101 - Document profiler use on Fenix, assist profiler workshop
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#100 - FNPRMS is missing results 4/9-4/12
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 9 comments
#99 - Increase stability of release criteria dashboard
Issue -
State: closed - Opened by mcomella almost 5 years ago
#98 - Breakdown April JIRA work
Issue -
State: closed - Opened by mcomella almost 5 years ago
#97 - Research how other apps measure startup performance
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 2 comments
#96 - Recalculate FNPRMS AL baseline on Fennec 68
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#95 - Unify existing FE perf docs
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 2 comments
#94 - Apply recent noise reduction learnings to FNPRMS
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#93 - Update SF FNPRMS to latest: run on fennecNightly, etc.
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 2 comments
#92 - FNPRMS HANOOB Fennec 68 baseline (G5) may be incorrect (lower than actual)
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 6 comments
#91 - FNPRMS HANOOB parsing logic is hard-coded to work on devices like G5
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#90 - Rerun FNPRMS for missing dates
Issue -
State: closed - Opened by ecsmyth almost 5 years ago
#89 - Make performance testing less confusing: write foundational docs (ready with tooling)
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#88 - Visual completeness time has high variance (16ms)
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#87 - FNPRMS performancetest intent doesn't bypass onboarding and fails to give Fully Drawn time for Hanoob
Issue -
State: closed - Opened by MarcLeclair almost 5 years ago
#86 - Add CI for FNPRMS
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#85 - Move FNPRMS into automation & ☁️ the cloud ☁️
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#84 - Improve reliability/robustness of FNPRMS: long term
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#83 - Improve reliability/robustness of FNPRMS: enough to gather data for other cold startup flows
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#82 - Determine confidence in browsertime dashboard numbers & document knowledge
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#81 - Determine confidence in FNPRMS dashboard numbers & document knowledge
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#80 - Determine how we should measure cold startup app link in the long term
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#79 - Determine the future for cold startup measurement tools (FNPRMS)
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#78 - Improve communication, working patterns with other teams
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#77 - Measure impact of collections on startup performance
Issue -
State: closed - Opened by ecsmyth almost 5 years ago
- 2 comments
#76 - Fix misc. FNPRMS issues
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#75 - Rerun FNPRMS on fennecBeta app link
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#74 - Validate new PageStop app link methodology
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#73 - Build visualization for Fenix page load telemetry
Issue -
State: open - Opened by ecsmyth almost 5 years ago
- 1 comment
#72 - Report time to first frame drawn in FNPRMS (M1)
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#71 - Get Fennec cold startup, applink baseline measurements from FNPRMS on the Pixel 2
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 2 comments
#70 - FNPRMS logs are very large, bloating results repository
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#69 - Run FNPRMS on fennecNightly builds on G5
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 8 comments
#68 - Repopulate missing FNPRMS data, or mark invalid
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 1 comment
#67 - FNPRMS stopped recording results on 2/14
Issue -
State: closed - Opened by mcomella almost 5 years ago
#66 - Getting Px2 numbers into FNPRMS nightly
Issue -
State: closed - Opened by MarcLeclair almost 5 years ago
- 3 comments
#65 - FNPRMS time calculation gives wrong readings for certain ranges.
Issue -
State: closed - Opened by MarcLeclair almost 5 years ago
#64 - Get comparable measurements to Fenix from Fennec release-like build, cold startup to homescreen
Issue -
State: closed - Opened by mcomella almost 5 years ago
- 3 comments
#63 - Build release-like build of Fennec for comparable measurements in FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 13 comments
#62 - Investigate Fennec telemetry
Issue -
State: open - Opened by ecsmyth about 5 years ago
- 1 comment
#61 - Output JSON from FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 3 comments
#60 - Enable developers to validate cold startup performance changes on WIP + document it
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#59 - Get fennec cold applink measurement from FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 2 comments
#58 - Document how to run FNPRMS locally
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#57 - Add Pixel 2 measurements to FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 6 comments
#56 - Add Beta & Release measurements to FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#55 - Begin reporting with FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#54 - Document unknowns with our FNPRMS measurement methodologies
Issue -
State: closed - Opened by mcomella about 5 years ago
- 4 comments
#53 - Review existing FNPRMS code
Issue -
State: closed - Opened by mcomella about 5 years ago
- 5 comments
#52 - Replace FNPRMS "AL" and "HA" with Intent names (VIEW & MAIN)
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#51 - Parameterize FNPRMS to run different variants
Issue -
State: closed - Opened by hawkinsw about 5 years ago
- 1 comment
Labels: enhancement
#50 - Determine what needs to be done to get comparable fennec measurements in FNPRMS
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#49 - Move FNPRMS to mozilla-mobile private repo
Issue -
State: closed - Opened by mcomella about 5 years ago
- 5 comments
#48 - Move FNPRMS to use Nightly builds
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#46 - Investigate how to interpret & utilize Google Play Vitals
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#45 - Mitigate randomized Experiment selection, feature flags for performance analysis
Issue -
State: closed - Opened by mcomella about 5 years ago
- 15 comments
#44 - Figure out how to make signing release builds easier for developers
Issue -
State: closed - Opened by mcomella about 5 years ago
- 3 comments
#43 - Get and distribute Fenix API tokens for local performance development
Issue -
State: closed - Opened by mcomella about 5 years ago
- 4 comments
#42 - Finalize cold startup measurement system for GA
Issue -
State: closed - Opened by mcomella about 5 years ago
- 7 comments
#39 - RecyclerView not set up correctly re-uses images for wrong viewHolder
Issue -
State: closed - Opened by MarcLeclair about 5 years ago
- 2 comments
Labels: bug
#37 - Add Support for Nightly Testing of Non-Onboarding Cold Start
Issue -
State: closed - Opened by hawkinsw about 5 years ago
- 2 comments
Labels: enhancement
#36 - Investigate meaning of 'Displayed'
Issue -
State: closed - Opened by hawkinsw about 5 years ago
- 2 comments
#35 - Investigate differences between force-stop and "normal" stop of an Android Task
Issue -
State: closed - Opened by hawkinsw about 5 years ago
- 2 comments
#33 - Gather preliminary numbers for hot start to home screen
Issue -
State: closed - Opened by mcomella about 5 years ago
- 4 comments
#32 - Gather preliminary numbers for cold app link
Issue -
State: closed - Opened by mcomella about 5 years ago
- 3 comments
#31 - Gather preliminary numbers for cold start to homescreen
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#30 - [team] Decide which metrics to focus on after gathering preliminary numbers
Issue -
State: closed - Opened by mcomella about 5 years ago
- 2 comments
#29 - Determine any special conditions Nimbledroid sets up during testing
Issue -
State: closed - Opened by mcomella about 5 years ago
- 2 comments
#27 - Potential slowdown from additional UI elements in the Home Fragment
Issue -
State: closed - Opened by hawkinsw about 5 years ago
- 1 comment
#26 - Create and share performance consultation process
Issue -
State: closed - Opened by mcomella about 5 years ago
- 3 comments
#25 - Add cold startup tests for Reference Browser
Issue -
State: closed - Opened by mcomella about 5 years ago
- 2 comments
#24 - Add hot start to app homescreen test for Fennec 68
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#23 - Measure baseline (Fennec 68) cold start to homescreen
Issue -
State: closed - Opened by mcomella about 5 years ago
- 2 comments
#22 - Check in on status of applink pageload test on BitBar
Issue -
State: closed - Opened by mcomella about 5 years ago
- 1 comment
#21 - Nimbledroid release uploads have stopped (Oct 29th edition)
Issue -
State: closed - Opened by mcomella about 5 years ago
- 5 comments
#20 - Nimbledroid nightly uploads have stopped (Oct 29th edition)
Issue -
State: closed - Opened by mcomella over 5 years ago
- 11 comments
#19 - Investigate Fenix, Fennec client telemetry
Issue -
State: closed - Opened by mcomella over 5 years ago
- 3 comments
#18 - [Nimbledroid] Question: do we want to run tests on Reference Browser or Sample Browser?
Issue -
State: closed - Opened by mcomella over 5 years ago
- 1 comment
#17 - [Nimbledroid] Investigate if "auto-discovered user flows" are useful
Issue -
State: closed - Opened by mcomella over 5 years ago
- 1 comment
#16 - [Nimbledroid] Investigate running tests on Android 7
Issue -
State: closed - Opened by mcomella over 5 years ago
- 7 comments
#15 - [Nimbledroid] Investigate uploading 64-bit APKs, if possible
Issue -
State: closed - Opened by mcomella over 5 years ago
- 2 comments
#14 - [Nimbledroid] Write custom test to understand how accessible that is
Issue -
State: closed - Opened by mcomella over 5 years ago
- 2 comments
#13 - [Nimbledroid] Enable alerting for regressions
Issue -
State: closed - Opened by mcomella over 5 years ago
- 7 comments
#12 - health.graphics is missing Nimbledroid uploads
Issue -
State: closed - Opened by mcomella over 5 years ago
- 6 comments
#11 - Investigate increased granularity on Nimbledroid results
Issue -
State: closed - Opened by mcomella over 5 years ago
- 7 comments
#10 - Investigate Nimbledroid low-hanging fruit
Issue -
State: closed - Opened by mcomella over 5 years ago
- 5 comments
#9 - Identify release criteria for Fenix GA
Issue -
State: closed - Opened by mcomella over 5 years ago
- 1 comment
#8 - Create preliminary roadmap; finalize Q4 perf OKRs
Issue -
State: closed - Opened by mcomella over 5 years ago
- 5 comments
#7 - TEST: verifying GitHub automation 3
Issue -
State: closed - Opened by mcomella over 5 years ago
#6 - TEST: verifying GitHub automation 2
Issue -
State: closed - Opened by mcomella over 5 years ago
#5 - TEST: verifying GitHub automation
Issue -
State: closed - Opened by mcomella over 5 years ago
#4 - Identify which features on Fenix roadmap may require perf analysis before their release
Issue -
State: closed - Opened by mcomella over 5 years ago
- 3 comments
#3 - Identify which test frameworks to invest in in Q1 2020 and beyond
Issue -
State: closed - Opened by mcomella over 5 years ago
- 1 comment
#2 - Create centralized list of mobile performance tests
Issue -
State: closed - Opened by mcomella over 5 years ago
- 3 comments
#1 - Investigate GitHub integration for Raptor, Nimbledroid per PR
Issue -
State: closed - Opened by mcomella over 5 years ago
- 6 comments