Profiling application under Wine

[Chambers, Matthew]

The application requires dotnet472 and 64-bit at that. I actually had to add that verb to winetricks to get our application to work. I'm 
definitely getting varying mileage! My question is how to profile it with Windows symbols so I can understand why and either help fix it in 
Wine or possibly avoid the problem from my application code.

On 6/25/2019 9:46 AM, Hin-Tak Leung wrote:
> Have you tried winetricks dotnet2 (if your application can run under dotnet2)? I have known quite a few dot net issues where running under wine-mono is a much slower than native dotnet2.
>
> dotnet2 runs quite okay on wine, and a lot faster, etc than wine-mono. There are some issues with running microsoft dotnet 3 and 4 under wine, so YMMV.
>
> --------------------------------------------
> On Mon, 24/6/19, Chambers, Matthew <matt.chambers42 at gmail.com> wrote:
>
>       Hi all,
>    
>       I have a scientific application which runs much slower under Wine
>       than on Windows for one type of data (read with a vendor's
>       closed-source .NET DLLs). For most other types of data (read with
>       other vendors' closed-source DLLs, some .NET, some not), the
>       performance is nearly the same. I'm trying to understand why. I have
>       run sysprof on both types of data trying to understand the
>       difference, but without the Windows symbols I don't really
>       understand what I'm looking at. I also ran perf and generated these
>       interactive flame graphs.
>    
>       Perf from the slow data vendor (Thermo):
>    
>       Perf from one of the fast data vendor (Bruker):
>    
>