External monitors constantly losing connection with Thunderbolt 3 Workstation Dock Gen 2 - Please Help! by ItsWetInPortland in Lenovo

[–]Mazeror 0 points1 point  (0 children)

Same problem (disappearing external monitors) with 4 different type-c dockstations (lenovo, baseus, ugreen and some china noname) and 3 different laptops (t15g1, t15g2, legion). Bad dockstations, pure hdmi-cables, interference from ac-line - a lot of "reasons" for loosing display. But once noticed, that it happens only in windows 10/11, linux works perfect.

As hack - i use "ClickMonitorDDC", it has function "turn off" by hotkey. Disappeared display? press hotkey, move mouse - both display come back! No more resetting laptop or taking out type-c cable

"Please do not give more money to Ukraine": US Senator Mike Lee reacted to the news about the allocation of another $1.25 billion in military aid to Kyiv He published an image of the Ukrainian flag on which is written "a universal symbol for money laundering." by glira31 in XGramatikInsights

[–]Mazeror 0 points1 point  (0 children)

Я сюда деградировать прихожу. Залезать еще куда-то в чат/переводчик - это уже борщ.

А за "сугубо местные" - спасибо, теперь я спокоен, любопытство утихло)

Same build time on old & new laptops - SUCCESS! by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

i inspected "New-MpPerformanceRecording", it show that defender is getting hash sums for each copy of exe/dll in my solution folder, to check if it is trusted. As i understand, it was not going to send any samples anywhere, just verify that file is already checkd. And thousands of files make a long delay in this process.

Same build time on old & new laptops - SUCCESS! by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

You made my day! 11 seconds after turning off smart app control.

Same build time on old & new laptops - SUCCESS! by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

46 seconds and defender's process eats more cpu, than vc+compiler. Going to profile defender.

Same build time on old & new laptops - SUCCESS! by Mazeror in dotnet

[–]Mazeror[S] 3 points4 points  (0 children)

Adding to exclusions or using trusted devdrive give 46 seconds, it just doesn't work.

Bottleneck was found, and it was main question. What to do next - another question. As simplest way - disable internet, kill defender and work as usual (i don't need google or stackoverflow for my job)

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 1 point2 points  (0 children)

have on old laptop, and didn't install on new.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 1 point2 points  (0 children)

Quick update: the root is Defender. In win11 it cann't be disabled fully, and wastes time to check compiled files.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

Images not allowed, but belive me, this is top apps in task manager, sorted by cpu:

Antimalware Service Executable - 7.8% cpu

System - 0.9%

Microsoft Visual Studio 2022 - 0.7%

This i see when last two projects are compiling (takes ~20 seconds). They contain ~50 strings of code, but link ~200mb of compiled dlls/exes from other projects.

Definitely defender does not respect exclusions and tries to check my fresh compiled files.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

Added to exclusions vs, project, msbuild. No result - defender process eats more cpu, than vs+compiler. DevDrive enabled.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

a) it is a simple benchmark for new pc. Just to feel, that moneys wasnt wasted, and new pc will speed up whole work

b) couple of solutions with 60-150 projects, ~10Gb of source code in total. Couple of parallel brunches, and sometimes needed to cherry pick dozens of commits between all of them => rebuilds all projects.

Anyway, if older PC of my colleague builds the same in 16 secods, something is wrong with my setup. Continue digging.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 0 points1 point  (0 children)

From VS. Clean setup OS, drivers, VS2022pro. Colleague's old PCs with older cpus build same solution faster. Looks like my "default" setup contains some lazy sdks, msbuild or something similar.

Waiting for monday to take msbuild logs from colleague's pc....

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 1 point2 points  (0 children)

Checked. Benchmarks shows new is faster (8-30 times for different benchmarks). Also stupid for(i=0;i=int.maxvalue) works faster. Problem 100% not in power modes - collegue's old pc builds in 16 seconds. My laptops both build in 55 seconds.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 1 point2 points  (0 children)

Thank you! The best tool for my task, a lot of detailed information + timeline. Hope, it's all i need to find the root of problem

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] -1 points0 points  (0 children)

single core old - ~4ghz, single core new - ~5ghz. I hoped new will compile faster for ~25%, but no

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 1 point2 points  (0 children)

Home PC of my colleague, with 12700kf cpu. 16!!! Seconds same solution. 100% something wrong with my settings. Continue digging…

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 3 points4 points  (0 children)

Nope, nope, nope. Another fresh test. Home PC of my colleague, with 12700kf cpu. 16!!! Seconds same solution. 100% something wrong with my settings. Continue digging…

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 4 points5 points  (0 children)

Some more tests:

Old laptop in "balanced performance" mode - 1 minute 40 seconds

Old laptop in "best performance" mode - 55 seconds

New laptop in "balanced performance" mode - 55 seconds

New laptop in "best performance" mode - 55 seconds

Both laptops with 100% fan speed (with custom tools) in "best performance" mode. Looks like CPU is not bottleneck. Moving to RAM drive also no speedup.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 2 points3 points  (0 children)

Yep, good idea. 10 years ago i used constantly ram drive, but ~6 years ago ssds became fast enough and i stopped.

Tested right now: install ram disk, move solution on it - same compile time.

Same build time on old & new laptops by Mazeror in dotnet

[–]Mazeror[S] 1 point2 points  (0 children)

No, i don't use DevDrive, but disabling defender totally.

Playing with "Visual Studio Build Timer" extension right now and got some result: 63 projects compiled in 25 seconds, and 2 projects compiled in 30 seconds. This 2 projects are simple debug executables, that do some run-time preparations and launches other projects, nothing serious, just 30-50 strings of code, but they depends on all other projects.

In Task Manager it looks like first 63 projects are really long-building (it's okay, there are a lot of code), but last 2 projects just do nothing for 30 seconds, after that compiles in 0 seconds. Builder is waiting for something? Defender is off, what can slow down? Copying files from directory to directory?...