Activity overview
Latest activity by GieltjE
This has been fixed by applying the AMD Agesa "Combo V2 PI 1.2.0.3 Patch B" update / comments
This has been fixed by applying the AMD Agesa "Combo V2 PI 1.2.0.3 Patch B" update
That is correct, so I lose 8 threads but the compilation time drops from ~30minutes to ~1.5 minutes. / comments
That is correct, so I lose 8 threads but the compilation time drops from ~30minutes to ~1.5 minutes.
Performance back to normal by disabling SMT. / comments
Performance back to normal by disabling SMT.
Even opening the saproj file takes about a minute for the splash screen to dissapear and building it via the gui takes about the same amount of time. Unfortunately we are not able to send our source files over. The strange part is that it does use a full thread of cpu usage, so it appears to be doing some calculation. How can we see which libraries are .NET2? As we should have migrated away from those a long, long time ago.
/ comments
Even opening the saproj file takes about a minute for the splash screen to dissapear and building it via the gui takes about the same amount of time. Unfortunately we are not able to send our sourc...
Both machines have all virusscanners disabled (including Windows defender), keep in mind that the i5-6600k is 20x faster so even if there was a virusscanner running there it's not slowing it down. Sent the procmon dump in a private message.
/ comments
Both machines have all virusscanners disabled (including Windows defender), keep in mind that the i5-6600k is 20x faster so even if there was a virusscanner running there it's not slowing it down.S...
Sent them in a private message / comments
Sent them in a private message
AMD performance 20x slower
Setups tested (All Win10-X64 Pro fully up to date 1909, plenty of spare ram and no other active processes, using the same .NET v4.8 project):
Intel i5-6600k
Intel i3-6320
AMD X6-1100T
AMD Ryzen 7 ...
@Russell D was reading the changelog and noticed a new build [image] / comments
@Russell D was reading the changelog and noticed a new build
6.12.1.641 fixes the issues / comments
6.12.1.641 fixes the issues
@Russell D Thanks for the reply, initially thought that I might have done something wrong somewhere.
Please let us know when the new version is fixed. / comments
@Russell D Thanks for the reply, initially thought that I might have done something wrong somewhere.
Please let us know when the new version is fixed.