HYDRA NEWS and information about WIN 11 (Patreon)

As many of you already know, every month I release an update for the HYDRA project. This month will be no exception and I want to share some information about the next update. HYDRA 1.0C PRO will arrive at the beginning or middle of next week. The main changes will be:

1. Redesigned mechanism for creating profiles. Profiles are now created based on CO tables. That is, the base frequencies of the profiles are higher, and HYDRA does not spend cycles to ramp frequencies. This has a significant impact on performance and reducing the CPU usage of the HYDRA application.

2. Each profile has 3 base frequencies for each CCD. Since the base frequency of the profiles will increase significantly we have a problem and what happens if the profile base frequency is oriented to AVX1 load and we include AVX2 or FMA3. This is why I implement the "sandwich" mechanism. Each profile in addition to the base AVX1 frequency will have a frequency for the extra light load SSE and for the extra heavy load AVX2-FMA3. But most importantly, the user does not have to do anything, no new settings are added (I know some of you are intimidated by the complexity of the project), all offsets are controlled automatically.

3. Frequency state memory for each load type. This means that HYDRA remembers frequencies for different load types and can quickly return to the saved value if the load conditions are similar to the load conditions during which the "save" was created. This has a significant impact on performance and reducing the CPU usage of the HYDRA application.

4 .Stability for mixed load. I know that some of you have complained about stability problems in LinX and other applications that alternate between super light and super heavy workloads. Crashes occurred because HYDRA did not have time to reduce the frequency (which was obtained with SSE load) when switching to AVX2/FMA3 state. Now during the presence of SSE load, HYDRA has a hard limit on the frequency increase, which allows a smoother transition to the AVX2/FMA3 state.

5. Added CO "alignment" function. Frequency lock mode is a new mode (for HYBRID OC) that may require a CO alignment operation to improve stability. What it means. After diagnostics, you get a report about CO and result frequencies that cores reach. Alignment mode allows you to find an overall satisfactory safe frequency for all cores in the CCD complex as well as recalculate CO. That is, we create a rule in which the best cores will not use a frequency that is unsafe for neighboring weaker cores in the CCD complex.

6. Checking Updates. In the presence of the Internet will prompt the user about the availability of updates, as well as display important information that I want you to quickly bring to you.

7. Find best voltages. This function has been redesigned and is able to provide the user with information about the best voltages and optimal voltages at which the processor operates with maximum energy efficiency. The user will also have energy efficiency metrics (MHz per 1mV and MHz per 1W for each CCD) available for each of the steps.

____________________

As for Windows 11.

What I see now is a very crude product, which has huge performance problems with Ryzen processors. AMD and MS are already preparing patches and some of them have already been published (October 12). Unfortunately, the patch only made the L3 delays worse.

AMD made a remark on social media that was shared on Reddit. The company stated that fixes for the two bugs are being developed and will be available soon. On October 21, the UEFI-CPPC2 bug patch will be released. AMD's "customers" include huge organizations who use Threadripper or EPYC workstations to conduct mission-critical workloads. On October 19, Windows Update will fix the L3 cache delay bug.

We'll wait.

____________________

I want to apologize that at the moment I can't always respond promptly. Moving into a new home is always difficult. If you have any questions, don't hesitate to write.

Thank you for your support!