microsoft / microsoft/perfview
perfcollect & PerfView: unable to get events working
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.7k
- Forks
- 775
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 9
Description
While working on https://github.com/dotnet/BenchmarkDotNet/pull/2117 I've very carefully followed the docs and have failed to get a trace file that contains events that could be successfully presented by PerfView. I've tried both x64 and arm64 Ubuntu machines.
The app that I've used:
string path = Path.Combine(Path.GetTempPath(), Path.GetRandomFileName());
string content = new string('a', 100_000);
for (int i = 0; i < 10_000; i++)
File.WriteAllText(path, content);
File.Delete(path);
Console.WriteLine("Done!");
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFrameworks>net5.0;net6.0;net7.0</TargetFrameworks>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
<LangVersion>Latest</LangVersion>
</PropertyGroup>
</Project>
The trace files I got:
net5.trace.zip
net6.trace.zip
net7rc1.trace.zip
@brianrob could you please take a look at these trace files and let me know if I am doing something wrong? I was expecting that with the default settings (COMPlus_PerfMapEnabled=1, COMPlus_EnableEventLog=1) some default events are going to be enabled and captured.
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
Start by opening the attached net5.trace.zip, net6.trace.zip, and net7rc1.trace.zip files in PerfView and compare the capture results with the documented perfcollect workflow and COMPlus_PerfMapEnabled and COMPlus_EnableEventLog settings. Done means identifying whether the traces are incorrectly captured or merely unreadable by PerfView, then documenting the cause or the required correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100