microsoft / microsoft/microsoft-performance-toolkit-sdk
DateTime wallclocks may not be precise enough, consider timestamps offset from Unix epoch instead?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 239
- Forks
- 78
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Description
This will be a breaking change, but one that we're willing to take given that it will allow greater precision going forward. We discussed two options:
1: The custom data processor converts all timestamps to be offsets from the unix epoch.
2: The custom data processor provides a wallclock before starting trace processing, and the runtime will do the conversion.
I'm not sure how #2 will work yet, we'll have to think that one through a bit more.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the custom data processor and runtime as the relevant entry points, but no files or tests are provided. First compare the two proposed Unix-epoch conversion approaches and determine the required breaking-change behavior; done requires an agreed design that provides greater timestamp precision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100