-
Just Updated my BIOS to AGESA 1.2.0.1. With (almost) the same settings, the growth in L3 performance is unbelievable! The 5000 series will be aging like fine wine, it seems.
-
This, so far, has no noticeable effect on anything besides AIDA64's benchmark, reflected in the change log for AGESA 1.2.0.1:
3) Improve L3$ bandwidth in AIDA64
ID: gq3pp8sID: gq4mnwsOkay, thanks for the clarification. I was hoping some gains in games and applications, but it seems it's just a fix.
Overall I think I have more stability with memory in boot sequence, but it's okay. I'm happy with that.
-
Yeah but does it actually improve anything in games ?
ID: gq4aoy3No, because it's literally only a fix for aida64
ID: gq3p84mI guess it will only show improvements on games (or applications) that will stress the cache. Perhaps a future game will be able to stress it.
Back then games didn't benefit faster RAM frequencies and lower latencies in the Sandy Bridge processors. Everybody back then ran DDR3 at 1333MHz. Now, 1866CL10+ is practically a necessity to make the classic CPU perform in modern titles to change the minimum FPS from 16 up to 30 or even 45fps.
All it takes is a newer game that will take advantage of the faster cache.
-
Jeez, dude, there is no improvement in performance. They just fixed a bug that messed with AIDA's memory/cache benchmark. No real world difference except for that particular test.
You know what would be nice though?
Fixing the damn WHEA interconnect problems for high IF clocks. -
The performance was already there it's just that AIDA64 wasn't reading it correctly/
-
Nothing to see here, it was probably just a misreporting. I saw a forum post where the AIDA64 devs claimed that it was difficult for the their algorithm to effectively measure bandwidth without cache thrashing on Zen 3's large 32MB L3, so something was probably changed in the AGESA so that the problem goes away.
-
Stop calling this fine wine. That’s just fanboy marking bullshit. It's more like filtering piss to drinkable water. AMD can't even fix the USB problems. if they manage to fix that would you also call that fine wine?
ID: gq5c71uI've been running a 5600X with a Asus B550 and have never had any USB issues either. It's weird how some people have issues and others don't when using the same hardware.
ID: gq642goHe's got a point
ID: gq5aqz2AMD can't even fix the USB problems. if they manage to fix that would you also call that fine wine?
Yes AMD has performance what is nice BUT anything else... feature and stability wise it is still far behind.
ID: gq4zj39Fine, I'll buy it.
First things first, didn't have any USB issues at any time, or probably I would be piss off to buy a 600€ CPU with design issues.
In the other hand, you should consider that if I didn't had any issues with my sample any update that give me more performance/score in tasks would be greatly welcome. OK?
I don't want to grow any "marketing-bullshit" like you say, but for me this is an improvement and NOTHING more. I'm sorry for the folks who are getting the annoying usb issues, but that doesn't affect me.
Greetings.
-
My motherboard just got the 1.2.0.0 update like two days ago, so looks like I'll be waiting a few months for this update
ID: gq4n8ckard just got the 1.2.0.0 update like two days ago, so looks like I'll be waiting a few months for this updat
Yes, and MSI took a couple of weeks to include the 1.2.0.1 update. Don't worry, I prefer MB manufacturers took their time working on the software rather than deploy some alpha builds and cause issues to the general user.
-
Looks like you got 600MB/s ram/mem bandwidth too even though for some reason it seems like it switched you from CR1 (1T?) to CR2
ID: gq4ndgcHe has it on auto.
ID: gq4nyu8Yes, I changed a couple of settings thanks to the "marvelous" BIOS importing option of MSI AGESA update that reset all configuration post-update (I managed to backup almost all settings though BIOS update, but forgot to switch to CR2 and add 75MHz OC in PBO.)
It's not a "100% fair" comparison, but the difference with each update is there.
-
AGESA 1.2.x.x for me has finally made it so my motherboard power stabilizes when running either XMP or SAM enabled on my 5600X and RX 6800. Before that enabling XMP without wattage tuning caused terrible mouse/keyboard input glitches and crashing. SAM did not work under any settings I tried until AGESA 1.2
All-in-all, it was a lifesaver, but it should not have had to have been when I had a B550, Zen 3, and RDNA2 but could not take advantage of an advertised feature of said setup.
-
Is there any difference in any other benchmark?
ID: gq4p67qProbably not, it's a fix in AIDA64 bench according to the changelog and some users.
In my personal experience the memory stability (POST) seems to be improved.
-
New benchmark score by hardware unboxed?
-
Is this also relevant for series 3000 cpus from amd?
ID: gq4odd4I don't think so. The changelog reports that this update (1.2.0.1) was a fix to AIDA64 benchmark. I guess didn't catch that before submitting this post in reddit.
But hey, at least got some stability with memory in boot sequences, that's fine.
-
:0
-
hmm overall latency is marginally higher with the newer version (likely within error) and write speeds are slower for Memory, L2 and L1 but read speeds have increased rather nicely.
Its interesting to see how they are making improvements across the versions.
Now if they could keep the higher read and write speeds while lower latency that would be nice too.
ID: gq4pkhjYes, and I'll took those differences with a grain of salt. You can check the 75MHz (cpu) difference and CR1 instead of CR2.
The RAM latency and subtimmings are the same on each case, just forgot to literally copy-paste those two settings through the new BIOS update, which resets all profiles and erase them.
-
My 5900x boost roughly 100mhz more multi core with 1.2.0.1 on my x570 tomahawk. Same CO. Benches reflect this. I'm Happy.
ID: gq4q4qdHey, that's great! My best OC'd up to date was 5,1GHz single core (with PBO+Curve Optimizer), but I don't need to reach that right now.
I prefer to get close to the 5GHz barrier and save some ºC(s) for the summer, which could be concerning because of temps.
ID: gq5oosiYeah I am also seeing this on my x570 tomahawk with 1.2.0.1.
I cam getting higher score in multi-threaded benchmarks across the board compared to 1.2.0.0.
-
Does this also affects Zen 2 ?
ID: gq4x4vbIt seems the AGESA 1.2.0.1 was a fix to AIDA64 L3 performance, but seems to have stability improvements with memory.
No it doesn't affect Zen 2 neither Zen 3 with other applications beyond AIDA64. Greetings.
-
I got a question for you guys. How much performance different do you think it would be between a ram 3600,16-19-19 vs 3733,16-16-16 for ryzen 5000?
-
Since I use mine mostly for rendering I'm more interested about CB results. I see a lot of complaints about reduced performance on AGESA1200+ so I'll hodl for now.
-
I dont know man, im just a bit worried if updating bios will destroy the peace that I have right now. is it all stable? have u ran stress tests?
ID: gq4qqpfDon't worry, the changelog reports this update fix some issues with AIDA64 detection, and other issues described.
You don't need to upgrade if necessary, just had more stability with memory on boot sequences and didn't have any issues post-update.
Also, take that with a grain of salt, didn't run any more benchmarks (CB, prime95, etc...) beyond this one. Greetings.
-
Set command rate to 1. You have it on auto. This should improve it even more.
ID: gq4r2bpThank you for the tip, I'll do it right now.
Forgot to change that one and PBO gains (+75MHz) with this AGESA update. Will report the results after that.
Greetings.
EDIT: nope, can't post with CR=1T, but fixed the PBO setting. Had some issues preventing POST previously and seems that can't force the memory up to that point.
For the record, have G.Skill TridentZ royal , (2x2 dual rank 3600CL17(2T)) OC'd to 3766cl16(1T). I'm fine with 1.36v, shouldn't brute-force to 1.4+ just to boot them. :S
-
Just give us access to public AGESA for us to write our own optimisations.
引用元:https://www.reddit.com/r/Amd/comments/lzqg7m/just_updated_my_bios_to_agesa_1201_with_almost/
Wow, when did they start publishing changelogs?