Open catapult-bot opened 9 years ago
catapult-bot
commented
9 years ago 
You'd also have to output the process/thread that each of those things started on, otherwise, why not just use an X event?
Something like:
{ph:'Y', stid:5, etid:6, spid:1, epid:2, name:'blah', ts:123, dur:24, ...}
Is there anything else that would be needed?
catapult-bot
commented
9 years ago 
Yes, it is doable. I can help with modifying the importer code if you decided to go with this route. What's the difference between tts and ts? "tts" is not explained in the docs, and it isn't very clear on what it does in the code either. Anyone knows?
catapult-bot
commented
9 years ago 
I believe ts is "timestamp" while tts is "thread timestamp". You can use tts to figure out how much time was actually spent running that thread.
On Mon, May 18, 2015 at 8:43 AM Helen Li notifications@github.com wrote:
Yes, it is doable. I can help with modifying the importer code if you decided to go with this route. What's the difference between tts and ts? "tts" is not explained in the docs https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/edit#heading=h.yr4qxyxotyw, and it isn't very clear on what it does in the code either. Anyone knows?
— Reply to this email directly or view it on GitHub https://github.com/google/trace-viewer/issues/960#issuecomment-103108581 .
catapult-bot
commented
9 years ago
A few folks have tracers that issue tons of async begin/end events. But, the async b and e end up duplicating a ton of data so the file gets le-big. The request from them is that we support a way to create an async event with a single event that contains a ts and a duration, like with 'X'
@xunjieli wdyt? Doable? We woudln't need to expose to chromium trace_event.h, just support it in the importer and update the format docs...