#dotmemory — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dotmemory, aggregated by home.social.
-
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here buff.ly/0VcasuN #dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
The Early Access Program for R... -
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here buff.ly/0VcasuN #dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
The Early Access Program for R... -
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here
#dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
-
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here
#dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
-
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here
#dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
-
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here
#dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
-
The Early Access Program for ReSharper and .NET Tools 2025.3 Is Here
#dotnet #resharper #visualstudio #csharp #dottrace #dotmemory
-
Having #dottrace and #dotmemory from #JetBrains is a godsend when solving production issues. #dotnet
-
Having #dottrace and #dotmemory from #JetBrains is a godsend when solving production issues. #dotnet
-
Having #dottrace and #dotmemory from #JetBrains is a godsend when solving production issues. #dotnet
-
Having #dottrace and #dotmemory from #JetBrains is a godsend when solving production issues. #dotnet
-
Having #dottrace and #dotmemory from #JetBrains is a godsend when solving production issues. #dotnet
-
Increase Your Odds to Find a Memory Leak With JetBrains #dotMemory - #dotNet
-
Increase Your Odds to Find a Memory Leak With JetBrains #dotMemory - #dotNet
-
Increase Your Odds to Find a Memory Leak With JetBrains #dotMemory - #dotNet
-
Increase Your Odds to Find a Memory Leak With JetBrains #dotMemory - #dotNet
-
Increase Your Odds to Find a Memory Leak With JetBrains #dotMemory - #dotNet
-
I just want to point out to #dotnet folks doing performance profiling that #dotMemory and #dotTrace work great cross-platform.
-
I just want to point out to #dotnet folks doing performance profiling that #dotMemory and #dotTrace work great cross-platform.
-
I just want to point out to #dotnet folks doing performance profiling that #dotMemory and #dotTrace work great cross-platform.
-
I just want to point out to #dotnet folks doing performance profiling that #dotMemory and #dotTrace work great cross-platform.
-
I just want to point out to #dotnet folks doing performance profiling that #dotMemory and #dotTrace work great cross-platform.
-
Ловушка бесконечно ленивого бассейна
Нечасто встречаются истории, когда причины и следствия сплетаются в один клубок, связывающий проблемы и с памятью, и с CPU, и с тредпулом. А инструментально затрагивающие и пулы объектов, и Lazy, и работу с асинхронностью, и длительные вычисления. А ещё реже встречаются те, где всё это распутывается и исправляется буквально несколькими строчками кода.
https://habr.com/ru/companies/skbkontur/articles/875514/
#net #c# #threadpool #c#net #производительность #dotmemory #performance
-
Ловушка бесконечно ленивого бассейна
Нечасто встречаются истории, когда причины и следствия сплетаются в один клубок, связывающий проблемы и с памятью, и с CPU, и с тредпулом. А инструментально затрагивающие и пулы объектов, и Lazy, и работу с асинхронностью, и длительные вычисления. А ещё реже встречаются те, где всё это распутывается и исправляется буквально несколькими строчками кода.
https://habr.com/ru/companies/skbkontur/articles/875514/
#net #c# #threadpool #c#net #производительность #dotmemory #performance
-
Ловушка бесконечно ленивого бассейна
Нечасто встречаются истории, когда причины и следствия сплетаются в один клубок, связывающий проблемы и с памятью, и с CPU, и с тредпулом. А инструментально затрагивающие и пулы объектов, и Lazy, и работу с асинхронностью, и длительные вычисления. А ещё реже встречаются те, где всё это распутывается и исправляется буквально несколькими строчками кода.
https://habr.com/ru/companies/skbkontur/articles/875514/
#net #c# #threadpool #c#net #производительность #dotmemory #performance
-
Ловушка бесконечно ленивого бассейна
Нечасто встречаются истории, когда причины и следствия сплетаются в один клубок, связывающий проблемы и с памятью, и с CPU, и с тредпулом. А инструментально затрагивающие и пулы объектов, и Lazy, и работу с асинхронностью, и длительные вычисления. А ещё реже встречаются те, где всё это распутывается и исправляется буквально несколькими строчками кода.
https://habr.com/ru/companies/skbkontur/articles/875514/
#net #c# #threadpool #c#net #производительность #dotmemory #performance
-
I have just published packages for #JetBrains #DataGrip, #dotTrace, #dotMemory, and #github-cli, for #Guix.
Previously packaged #Rider and #dotnet, and things are looking promising for developing .NET on Guix.
I probably won't have time to test it properly until January,
Get some errors when trying Azure CLI, so I need to look closer into that.
#mono is notably missing, but I'm confused about Mono Project, #wine fork and the .NET runtime mono repository.
-
I have just published packages for #JetBrains #DataGrip, #dotTrace, #dotMemory, and #github-cli, for #Guix.
Previously packaged #Rider and #dotnet, and things are looking promising for developing .NET on Guix.
I probably won't have time to test it properly until January,
Get some errors when trying Azure CLI, so I need to look closer into that.
#mono is notably missing, but I'm confused about Mono Project, #wine fork and the .NET runtime mono repository.
-
I have just published packages for #JetBrains #DataGrip, #dotTrace, #dotMemory, and #github-cli, for #Guix.
Previously packaged #Rider and #dotnet, and things are looking promising for developing .NET on Guix.
I probably won't have time to test it properly until January,
Get some errors when trying Azure CLI, so I need to look closer into that.
#mono is notably missing, but I'm confused about Mono Project, #wine fork and the .NET runtime mono repository.
-
I have just published packages for #JetBrains #DataGrip, #dotTrace, #dotMemory, and #github-cli, for #Guix.
Previously packaged #Rider and #dotnet, and things are looking promising for developing .NET on Guix.
I probably won't have time to test it properly until January,
Get some errors when trying Azure CLI, so I need to look closer into that.
#mono is notably missing, but I'm confused about Mono Project, #wine fork and the .NET runtime mono repository.
-
I have just published packages for #JetBrains #DataGrip, #dotTrace, #dotMemory, and #github-cli, for #Guix.
Previously packaged #Rider and #dotnet, and things are looking promising for developing .NET on Guix.
I probably won't have time to test it properly until January,
Get some errors when trying Azure CLI, so I need to look closer into that.
#mono is notably missing, but I'm confused about Mono Project, #wine fork and the .NET runtime mono repository.
-
The ReSharper and the .NET Tools 2024.3 Release Candidates Are Now Available.
https://blog.jetbrains.com/dotnet/2024/11/07/rsrp-net-tools-2024-3-rc/
#dotnet #resharper #dottrace #dotpeek #dotmemory #productivity #jetbrains -
The ReSharper and the .NET Tools 2024.3 Release Candidates Are Now Available.
https://blog.jetbrains.com/dotnet/2024/11/07/rsrp-net-tools-2024-3-rc/
#dotnet #resharper #dottrace #dotpeek #dotmemory #productivity #jetbrains -
The ReSharper and the .NET Tools 2024.3 Release Candidates Are Now Available.
https://blog.jetbrains.com/dotnet/2024/11/07/rsrp-net-tools-2024-3-rc/
#dotnet #resharper #dottrace #dotpeek #dotmemory #productivity #jetbrains -
The ReSharper and the .NET Tools 2024.3 Release Candidates Are Now Available.
https://blog.jetbrains.com/dotnet/2024/11/07/rsrp-net-tools-2024-3-rc/
#dotnet #resharper #dottrace #dotpeek #dotmemory #productivity #jetbrains -
The ReSharper and the .NET Tools 2024.3 Release Candidates Are Now Available.
https://blog.jetbrains.com/dotnet/2024/11/07/rsrp-net-tools-2024-3-rc/
#dotnet #resharper #dottrace #dotpeek #dotmemory #productivity #jetbrains -
Finding memory leaks in your #dotnet applications with #dotMemory be like.
-
Finding memory leaks in your #dotnet applications with #dotMemory be like.
-
Finding memory leaks in your #dotnet applications with #dotMemory be like.
-
Finding memory leaks in your #dotnet applications with #dotMemory be like.
-
Finding memory leaks in your #dotnet applications with #dotMemory be like.
-
I’m testing the #dotMemory integration in #JetBrainsRider for #dotnet stuff, and I knew it was not good to have LINQ in your hot paths, but this is surprising after a refactor.
- Removed an anonymous object allocation
- Switched to for loopsResults:
- LINQ: 10 million object allocations and 1 minute to execute
- For loops: 2 Million objects and 15 seconds to execute -
I’m testing the #dotMemory integration in #JetBrainsRider for #dotnet stuff, and I knew it was not good to have LINQ in your hot paths, but this is surprising after a refactor.
- Removed an anonymous object allocation
- Switched to for loopsResults:
- LINQ: 10 million object allocations and 1 minute to execute
- For loops: 2 Million objects and 15 seconds to execute -
I’m testing the #dotMemory integration in #JetBrainsRider for #dotnet stuff, and I knew it was not good to have LINQ in your hot paths, but this is surprising after a refactor.
- Removed an anonymous object allocation
- Switched to for loopsResults:
- LINQ: 10 million object allocations and 1 minute to execute
- For loops: 2 Million objects and 15 seconds to execute -
I’m testing the #dotMemory integration in #JetBrainsRider for #dotnet stuff, and I knew it was not good to have LINQ in your hot paths, but this is surprising after a refactor.
- Removed an anonymous object allocation
- Switched to for loopsResults:
- LINQ: 10 million object allocations and 1 minute to execute
- For loops: 2 Million objects and 15 seconds to execute -
I’m testing the #dotMemory integration in #JetBrainsRider for #dotnet stuff, and I knew it was not good to have LINQ in your hot paths, but this is surprising after a refactor.
- Removed an anonymous object allocation
- Switched to for loopsResults:
- LINQ: 10 million object allocations and 1 minute to execute
- For loops: 2 Million objects and 15 seconds to execute -
I’m reading up on profiling tools like #dotTrace and #dotMemory and realized that #dotnet and #csharp collection expressions might be the source of many performance headaches.
The main reason is you can't specify a collection size, which means the underlying array will likely go through a few resizes.
-
I’m reading up on profiling tools like #dotTrace and #dotMemory and realized that #dotnet and #csharp collection expressions might be the source of many performance headaches.
The main reason is you can't specify a collection size, which means the underlying array will likely go through a few resizes.
-
I’m reading up on profiling tools like #dotTrace and #dotMemory and realized that #dotnet and #csharp collection expressions might be the source of many performance headaches.
The main reason is you can't specify a collection size, which means the underlying array will likely go through a few resizes.
-
I’m reading up on profiling tools like #dotTrace and #dotMemory and realized that #dotnet and #csharp collection expressions might be the source of many performance headaches.
The main reason is you can't specify a collection size, which means the underlying array will likely go through a few resizes.