Deprecated Catapult GitHub. Please instead use http://crbug.com "Speed>Benchmarks" component for bugs and https://chromium.googlesource.com/catapult for downloading and editing source code..
Home Page: https://chromium.googlesource.com/catapult
License: BSD 3-Clause "New" or "Revised" License
Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:
These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.
Please see our contributor's guide
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#25
From [email protected] on May 31, 2012 13:06:19
timeline analysis should be expandable
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=18
We should have a script that fetches the right binaries from the buildbots and patches them in, or just syncs the v8 code at the given revision and builds them itself.
We could either run this regularly as a cron job (see https://code.google.com/p/chromium/codesearch#chromium/build/scripts/slave/recipes/catapult_cron.py) or make it so that we can run these as a tryjob on an as-needed basis.
We already have linux, windows, and mac slaves, so the buildbot part of this is not blocked, but I think ideally we would also have d8_runner use the new binary dependency system @Apeliotes is working on.
Monday Sep 22, 2014 at 19:53 GMT
Originally opened as google/trace-viewer#16
From [email protected] on April 25, 2012 14:50:31
How about an option to show the event args in the selection summary? It's often tedious to narrow the selection to only one event in order to see its args.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=9
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#43
From [email protected] on June 13, 2012 11:43:24
The trace format changed in 3.4; need to update the linux importer to handle it.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=37
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#36
From [email protected] on June 09, 2012 02:36:24
We currently have to hand-specify each and every .js file that we need when using tracing. This is cumbersome and discourages adding new files to the project. We can do better.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=30
Friday Sep 19, 2014 at 05:35 GMT
Originally opened as google/trace-viewer#4
...ly
On clicking scroll bar of 'timing mode', thread times window is shifting to
right side and user is unable to scroll down. We are assuming that every hit
in timing mode is on the canvas area itself and moving to setting the interest
range value including that the range right is being selected. Do the interest
range actions only if the mousedown hit point is in the canvas rect.
BUG=549
kphanee included the following code: https://github.com/google/trace-viewer/pull/4/commits
Friday Sep 19, 2014 at 15:17 GMT
Originally opened as google/trace-viewer#6
On clicking scroll bar of 'timing mode', thread times window is shifting to
right side and user is unable to scroll down. We are assuming that every hit
in timing mode is on the canvas area itself and moving to setting the interest
range value including that the range right is being selected. Do the interest
range actions only if the mousedown hit point is in the canvas rect.
BUG=549
kphanee included the following code: https://github.com/google/trace-viewer/pull/6/commits
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#33
From [email protected] on July 26, 2011 10:36:36
Select some events, then click a button that hides all other events that don't match the set of selected names. This helps when you find the event, but not the exact one you're looking for.
This could be done in a more generic way, with a text field to search for events and filter in/out etc.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=26
Monday Sep 22, 2014 at 19:53 GMT
Originally opened as google/trace-viewer#15
From [email protected] on April 25, 2012 14:28:16
Currently the processes and threads are ordered by pid/tid in about:tracing, but this can change each time chrome starts. Ideally, we would always list threads in creation/ownership order, such as:
browser
renderer
renderer
...
gpu
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=8
Friday Sep 19, 2014 at 15:16 GMT
Originally opened as google/trace-viewer#5
Track contents drawing function is draw_() instead of drawTrackContents_().
Call to invalid function drawTrackContents_() is causing failure of performance tests:
tracing.tracks.drawing_container_perf_test.draw_softwareCanvas_1
tracing.tracks.drawing_container_perf_test.draw_softwareCanvas_10
tracing.tracks.drawing_container_perf_test.draw_softwareCanvas_100
drawTrackContents_() was renamed to draw_() as part of revision 1544 - Add collapsing to most tracks in the timeline
kphanee included the following code: https://github.com/google/trace-viewer/pull/5/commits
Monday Sep 22, 2014 at 19:56 GMT
Originally opened as google/trace-viewer#50
From [email protected] on June 16, 2012 22:52:25
unittest.assertArrayEquals currently does a shallow test
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=44
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#24
From [email protected] on May 31, 2012 11:09:04
I opened up tracing and it was hard to find the help button.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=17
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#31
From [email protected] on June 06, 2012 10:32:42
'Selected item' text area is viewable but not selectable, so you can't copy/paste. At some point selecting was allowed, IIRC.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=24
Monday Sep 22, 2014 at 19:52 GMT
Originally opened as google/trace-viewer#12
From [email protected] on August 02, 2011 14:15:38
As well as the graphical view, it would be useful to have a summary of each event in the capture including at least the following:
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=5
Monday Sep 22, 2014 at 19:52 GMT
Originally opened as google/trace-viewer#10
From [email protected] on August 02, 2011 14:00:12
After a run of trace_events, there may be hundreds of events and finding the ones you are interested in can be difficult. This issue will only increase as the feature gains popularity.
By displaying a tree of categories and events and allowing it to be used as a filter, only the events that a user is interested in need be displayed.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=3
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#29
From [email protected] on June 05, 2012 00:16:51
The SliceTracks's setter should go through each of its slices and verify that the starts and end times are monotonically increasing. The fastRectRenderer fails if that assumption is not held.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=22
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#44
From [email protected] on June 13, 2012 15:15:16
It's a bit difficult to test the output code in timeline_analysis.js. Refactor it to be more testable.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=38
Monday Sep 22, 2014 at 19:53 GMT
Originally opened as google/trace-viewer#18
From [email protected] on May 20, 2012 13:38:11
Expected result: the track closes and the 'X' for the track below the one that was deleted is under the mouse cursor
What actually happens: the track closes but the scroll view pops up to the top. The mouse cursor is over a random track.
Use case: often, you want to hide many tracks at once, by just clicking the 'x' over and over again. Because scroll jumps, this is not possible.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=11
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#41
From [email protected] on June 09, 2012 02:48:39
We should not allow linty code to get committed.
Copy chrome:src/chrome/browser/resources/PRESUBMIT.py into this repo.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=35
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#23
From [email protected] on May 31, 2012 11:07:10
Open up help in about:tracing
It's unclear how to exit
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=16
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#26
From [email protected] on May 31, 2012 13:46:27
At the risk of opening pandora's box, I'd like some way of using dvorak with about:tracing. One way would be to just map those keys in addition to the normal wasd. Here's the dvorak keys that map to wasd:
, up
a left
o down
e right
Note that 'a' is the same. 'e' is already used. It seems to go left more than 'a' does. Not sure why or if this is required. If it's rarely used, maybe we can just dump it.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=19
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#34
From [email protected] on February 03, 2012 18:07:39
What steps will reproduce the problem? 1. Open about:tracing
2. Start / stop trace
3. Click any event
4. Double click name of event. What is the expected output? What do you see instead? Expected: Name is selected, nothing else happens. Instead, the name is selected and the UI executes a zoom in.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=28
Monday Sep 22, 2014 at 19:56 GMT
Originally opened as google/trace-viewer#45
From [email protected] on June 13, 2012 15:17:06
Add more unit tests to timeline_analysis.js for various selections. For example, multiple counter events, counter events and normal events, etc.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=39
Monday Sep 22, 2014 at 19:56 GMT
Originally opened as google/trace-viewer#49
From [email protected] on June 16, 2012 22:21:46
When trace-viewer was in the chrome repo, we picked up presubmit checks for both javascript and css lint. We should try to bring those back online.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=43
Monday Sep 22, 2014 at 19:52 GMT
Originally opened as google/trace-viewer#13
From [email protected] on September 29, 2011 14:27:11
Show the trace event category for events in about:tracing
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=6
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#30
From [email protected] on June 05, 2012 13:13:11
The createSummaryElementForSelection uses a variety of appendXXX methods. These methods construct elements and return them which is awesome but it makes it hard to test the analysis code.
We should create a class
SummaryBuilder {
}
SummaryBuilder.prototype = {
// all the append methods
}
And modify createSummaryElementForSelection to take a SummaryBuilder instance as one of its arguments.
This way, when we want to test code, e.g. the averaging code, we can pass in a mock version of this interface instead.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=23
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#40
From [email protected] on June 09, 2012 02:46:05
Right now, when you hide a track, it comes right back when you load another file. We should try to persist these hiding actions, when possible.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=34
Friday Sep 19, 2014 at 15:25 GMT
Originally opened as google/trace-viewer#7
kphanee included the following code: https://github.com/google/trace-viewer/pull/7/commits
Reason: Polymer 1.0+ is actively maintained (and has better performance than Polymer 0.5).
The Polymer team made a tool called polyup to automate some of the relatively straightforward parts of the process: http://polymerlabs.github.io/polyup/. Some other things will have to be done manually, as described in https://www.polymer-project.org/1.0/docs/migration.html.
I'm working on making the following tracing tests run on the catapult waterfall:
https://github.com/google/trace-viewer/blob/master/tracing/run_d8_tests
https://github.com/google/trace-viewer/blob/master/tracing/run_py_tests
https://github.com/google/trace-viewer/blob/master/tracing/build/run_dev_server_tests
The first two scripts call install_hooks.InstallHooks(). I am assuming this is only needed for local testing. Is it okay to add a flag like --is-buildbot (naming suggestions welcome) that skips this?
Monday Sep 22, 2014 at 19:52 GMT
Originally opened as google/trace-viewer#11
From [email protected] on August 02, 2011 14:08:35
A long trace might benefit from being split into logical frames. This requires a special event or function to be designated the 'end of frame'. The UI can then allow paging between frames which will make the trace much easier to navigate.
This doesn't make sense for all processes and some events may span frame boundaries, but that shouldn't be an issue as the underlying data should be stored the same and just presented as multiple frames.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=4
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#28
From [email protected] on May 31, 2012 15:05:20
ruler should stay in view when threads are scrolled
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=21
Monday Sep 22, 2014 at 19:53 GMT
Originally opened as google/trace-viewer#14
From [email protected] on April 25, 2012 14:28:16
Currently the processes and threads are ordered by pid/tid in about:tracing, but this can change each time chrome starts. Ideally, we would always list threads in creation/ownership order, such as:
browser
renderer
renderer
...
gpu
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=7
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#27
From [email protected] on May 31, 2012 15:02:35
The search box looks like it could use some love in general. At one point I couldn't focus it at all (not sure of repro steps). It can also be tricky to see the number of results in the background or to navigate the results when they exist.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=20
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#37
From [email protected] on June 09, 2012 02:39:57
There's good changes made to linux_perf_importer as part of systrace that we should get upstreamed.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=31
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#22
From [email protected] on May 24, 2012 16:44:15
Once we have parsed async slices, we currently always add them to the thread's async slice group.
When we see slices that start and end on a thread, we should still do this.
For slices that start on one thread and end on another, we should instead draw arrows between threads.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=15
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#21
From [email protected] on May 24, 2012 16:40:17
When there are import errors, we should show a little red (!) icon somewhere in the tracing button bar that when clicked will show the import errors.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=14
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#38
From [email protected] on June 09, 2012 02:43:08
TimelineViewport assumes the display refreshes at 60hz.
On most platforms, the trace contains information about the real refresh rate. We should find that information and adjust the grid frequency accordingly.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=32
Monday Sep 22, 2014 at 19:56 GMT
Originally opened as google/trace-viewer#48
From [email protected] on June 16, 2012 22:20:21
The statement
throw 'someError'
does not capture a stack trace.
Whereas:
throw new Error('someError')
Does.
We should change to using error objects.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=42
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#32
From [email protected] on July 26, 2011 10:18:01
Quite often, a selection contains only a few items, and it's difficult to zoom in far enough to narrow down the selection to one item. Yet, we still want to see the argument values of one of the selected trace items.
In the selection summary, one option is to allow the user to click a down arrow next to a selected item to see all instances of it and their argument values in drop down (or just expanded) list.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=25
Monday Sep 22, 2014 at 19:56 GMT
Originally opened as google/trace-viewer#47
From [email protected] on June 16, 2012 02:46:04
We shouldn't add the *Totals row when we've got just one result. It doesn't provide useful information.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=41
Monday Sep 22, 2014 at 19:53 GMT
Originally opened as google/trace-viewer#17
From [email protected] on May 16, 2012 15:55:52
E.g. finding 5110.937 should pan the timeline view to 5110.937 and put a line there or something.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=10
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#35
From [email protected] on June 09, 2012 02:35:18
linux_perf_importer has grown a bit organically. Lets get it cleaned up to be a bit more maintainable.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=29
Monday Sep 22, 2014 at 19:56 GMT
Originally opened as google/trace-viewer#46
From [email protected] on June 14, 2012 00:41:38
TimelineView is currently the "base class" of all our UI, holding a Timeline and TimelineAnalysis. But, then we have this Timeline, which is actually the widget that shows the tracks. We should probably clean this up, such that Timeline is the base UI component. TBD what to do with the current code called Timeline. Maybe rename that to TimelineTracksView.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=40
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#19
From [email protected] on May 22, 2012 01:37:51
linux_perf_importer does not handle sched_wakeups. This causes us to report threads as sleeping longer than they should be.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=12
Monday Sep 22, 2014 at 19:52 GMT
Originally opened as google/trace-viewer#9
From [email protected] on May 06, 2011 14:14:23
Certain events need to stand out in the UI more than others. It would be helpful to be able to specify that to the trace macro somehow.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=2
Monday Sep 22, 2014 at 19:52 GMT
Originally opened as google/trace-viewer#8
From [email protected] on August 02, 2011 13:47:27
Clicking and dragging in the page should scroll around.
Mouse wheel should zoom when a modifier is present (shift?).
Double-click should zoom to a block.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=1
Monday Sep 22, 2014 at 19:54 GMT
Originally opened as google/trace-viewer#20
From [email protected] on May 22, 2012 01:37:51
linux_perf_importer does not handle sched_wakeups. This causes us to report threads as sleeping longer than they should be.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=13
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#39
From [email protected] on June 09, 2012 02:46:05
Right now, when you hide a track, it comes right back when you load another file. We should try to persist these hiding actions, when possible.
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=33
Monday Sep 22, 2014 at 19:55 GMT
Originally opened as google/trace-viewer#42
From [email protected] on June 11, 2012 09:09:20
"W, A, S, D keys are specific for qwerty keyboards. It is quite hard to manipulate with different keyboard layouts from other countries. It would be nice if you could support the arrows keys." - Jerome Etienne http://www.html5rocks.com/en/tutorials/games/abouttracing/
Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=36
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
