Friday, January 14th 2022

RAMP is AMD's Answer to Intel's XMP for DDR5

Based on details from multiple sources, least not the release notes for HWiNFO 7.17 beta, we now know that AMD is working on an answer to Intel's XMP memory profiles that should be called RAMP, or Ryzen Accelerated Memory Profile. Not much is known about RAMP at this point in time, but hopefully it'll be as straightforward to use as Intel's XMP when it comes to configuring overclocked DIMMs.

Intel has of course updated XMP to version 3.0 which includes support for DDR5 memory, although it was reported that Intel was late when it came to finalising the specifics of XMP 3.0, which meant some early DDR5 modules intended for overclocking didn't end up getting any XMP profiles. Hopefully AMD will get its RAMP spec finished well ahead of time, so the memory makers that want to offer support for RAMP can do so well ahead of the launch of AMD's upcoming AM5 platform.
Sources: HWiNFO, via VideoCardz
Add your own comment

40 Comments on RAMP is AMD's Answer to Intel's XMP for DDR5

#1
Chaitanya
Most non tech people are going to confuse it with Ramps seen in daily life.
Posted on Reply
#2
MrDweezil
Doesn't XMP more or less already work on AMD boards?
Posted on Reply
#4
ncrs
MrDweezilDoesn't XMP more or less already work on AMD boards?
Exactly "more or less" - it depends on the board vendor. Since XMP requires royalties it's something that can be skipped by some vendors.
AMD's equivalent to XMP was AMP (which used to be described at www.amd.com/en-gb/innovations/software-technologies/amp but not any more, it's still in the WaybackMachine), for XMP 3.0 it seems to be RAMP.
DeathtoGnomesI suppose this replaces DOCP?
DOCP and equivalents (like EOCP for Gigabyte) was a way to skip paying XMP royalties, but still using the XMP data.
Posted on Reply
#5
Chrispy_
ncrsDOCP and equivalents (like EOCP for Gigabyte) was a way to skip paying XMP royalties, but still using the XMP data.
Oh god, I forgot that XMP had royalties!

All because JEDEC can't be bothered to create a spec that includes timings and not just frequency!
Posted on Reply
#6
Punkenjoy
seth1911AMD cant accept that XMP is the standard for OC RAM, they need anything else.
Maybe this dumbass Company should get to work XMP Profiles.

But yeah they need own profiles cause the 12100F fucks every 3xxx Series straigt off incl. the 5000G n the CPU Performance in Games.

OHHHHH wait AMD didnt release any Quad Core to Consumer since the 3100 or 3300X,
dumbass company for life.
Before calling other names, you should know that it's not XMP but Intel XMP. This is an Intel registred name. AMD support it under other names. And after that, good that a CPU release in 2022 beat CPU released in 2019
Posted on Reply
#7
Turmania
AMD says no Intel has had it for 10 years but we will do our own. and ramp up prices with ramp memory modules... and the fanboyz are all excited... there is no need for this shanigans.
Posted on Reply
#8
bug
And only 4 years late for the party. Users have had a world of grief trying to run overclocked memory on Zen CPUs.
Just look up "sorry, your memory is not on the QVL of that board" replies in these forums. It got better with Zen iterations, but it was pretty bad at first. RAMP should have been released alongside Zen.
Posted on Reply
#9
windwhirl
This should be standardized inside JEDEC already. And for that matter, every module should work perfectly fine out of the box on every board. No one should have to even consider looking into QVLs to see if a module works or not.
seth1911Oh no 2022 Quadcore beat Eightcore from 2019, ohhh no AMD didnt release any Quadcore since the 31/33X,
please dont cry me a river :cry:
Oh, for pete's sake, you started with the shilling in this thread. Don't be an hypocrite.
Posted on Reply
#10
xBruce88x
In before intel announces Greater Intel Memory Profile or GIMP lol
Posted on Reply
#11
ModEl4
Why Ryzen (Ramp) and not something more generic, regarding long term cpu plans don't they have anything after the zen-core based era? jk
Posted on Reply
#12
windwhirl
ModEl4Why Ryzen (Ramp) and not something more generic, regarding long term cpu plans don't they have anything after the zen-core based era? jk
They already are working on Zen 8, no joke.

On the other hand, you have Intel using the Core brand since 2006 or so...
Posted on Reply
#13
mechtech
Chrispy_Oh god, I forgot that XMP had royalties!

All because JEDEC can't be bothered to create a spec that includes timings and not just frequency!
Intel loves royalties.

and yes. JEDEC really does need to standardize more freq/timings profiles.

and ram should be priced, marketed and sold by/at jedec speeds, not xmp profiles.
Posted on Reply
#14
bug
windwhirlThis should be standardized inside JEDEC already. And for that matter, every module should work perfectly fine out of the box on every board. No one should have to even consider looking into QVLs to see if a module works or not.
That's exactly how it works: memory runs out of the box at the highest JEDEC standard it supports.
It's just that Zen requires running RAM well outside JEDEC spec to get the most out of it and up until now, AMD provided no guidance for that.

As for why JEDEC doesn't standardizes faster RAM I don't know and I don't have enough knowledge of the process or technology to venture a guess.
Posted on Reply
#15
Wirko
Chrispy_All because JEDEC can't be bothered to create a spec that includes timings and not just frequency!
It does include timings. DDR4-3200W stands for 20-20-20, for example. But that's the fastest example of all.

For anything above 3200 ... It's chicken and egg. CPU official specs don't go above that for DDR4. Motherboard manuals mention anything over 3200 as overclocking, with no guaranteed speed given. And JEDEC is a standards body. Why would a standards body care about overclocking?
Posted on Reply
#16
TheLostSwede
bugThat's exactly how it works: memory runs out of the box at the highest JEDEC standard it supports.
It's just that Zen requires running RAM well outside JEDEC spec to get the most out of it and up until now, AMD provided no guidance for that.

As for why JEDEC doesn't standardizes faster RAM I don't know and I don't have enough knowledge of the process or technology to venture a guess.
Except that's kind not how it works. Even new sticks of RAM are limited to 2133 MHz, when they can run at 4400 MHz XMP. So in reality that RAM should be running at 3200 MHz JEDEC as a minimum, but alas, the DIMM makers simply don't bother, as they know their customers don't care about the JEDEC profiles.
On top of that, as pointed out above, JEDEC timings are a joke, for example, the tightest JEDEC 3200 MHz timings are 20-20-20, when some higher-end modules can do 14-14-14 at 3600 MHz.
So what you think happens, doesn't happen.
Posted on Reply
#17
bug
TheLostSwedeExcept that's kind not how it works. Even new sticks of RAM are limited to 2133 MHz, when they can run at 4400 MHz XMP. So in reality that RAM should be running at 3200 MHz JEDEC as a minimum, but alas, the DIMM makers simply don't bother, as they know their customers don't care about the JEDEC profiles.
On top of that, as pointed out above, JEDEC timings are a joke, for example, the tightest JEDEC 3200 MHz timings are 20-20-20, when some higher-end modules can do 14-14-14 at 3600 MHz.
So what you think happens, doesn't happen.
Bummer. Haven't changed RAM in a while and it shows.
Is this on the DIMM makers though? Or is it the mobos/UEFIs?
Posted on Reply
#18
AsRock
TPU addict
MrDweezilDoesn't XMP more or less already work on AMD boards?
It don't on mine.
Posted on Reply
#19
Chrispy_
WirkoIt does include timings. DDR4-3200W stands for 20-20-20, for example. But that's the fastest example of all.

For anything above 3200 ... It's chicken and egg. CPU official specs don't go above that for DDR4. Motherboard manuals mention anything over 3200 as overclocking, with no guaranteed speed given. And JEDEC is a standards body. Why would a standards body care about overclocking?
Jedec includes timings, but timings are fixed to 12.5ns at the fast end, and 15ns at the slow end.


JEDEC hasn't updated or added to that since 2014 so now most RAM runs faster than this with 8-10ns latency.
Cheap stuff like 3200 CL16 and 3600 CL17 is 10ns and 9.4ns respectively. JEDEC timings are slower than that slow stuff, stuck in 2014.

My criticism of JEDEC is in neglecting to evolve the standard over time. They have suffixes for tighter timings but never go faster than 12.5ns when manufacturing moved on and left 12.5-15ns DIMMS in the history books. XMP came about because Intel got pissed waiting for JEDEC to do their job, and it's a good thing they didn't wait for JEDEC either because 8 years later they've still done fuck all.
Posted on Reply
#20
Makaveli
seth1911AMD cant accept that XMP is the standard for OC RAM, they need anything else.
Maybe this dumbass Company should get to work XMP Profiles.

But yeah they need own profiles cause the 12100F fucks every 3xxx Series straigt off incl. the 5000G n the CPU Performance in Games.

OHHHHH wait AMD didnt release any Quad Core to Consumer since the 3100 or 3300X,
dumbass company for life.
lol this is the best I don't know what i'm talking about post today i've seen.
Posted on Reply
#21
mechtech
ChaitanyaMost non tech people are going to confuse it with Ramps seen in daily life.
Sadly I see a lot of every day non tech & tech people that don't even know what a ramp is...........................
Posted on Reply
#22
mama
Sounds great. AMD developing it's own ecosystem which will only compliment their hardware. SAM as another example.
Posted on Reply
#23
Divide Overflow
MrDweezilDoesn't XMP more or less already work on AMD boards?
Works fine for me. XMP profile enabled.

Posted on Reply
#24
damric
Before bitching about JEDEC, go join JEDEC. It's free and you can read the newsletter they email you once in a while. There's good engineering articles about what you'll be seeing soon, and many of your questions might be answered. Of course you might learn something and then have even more questions, but at least you won't be bitching on the forum about the bare minimum reliability standard for memory.
Posted on Reply
#25
xBruce88x
AsRockIt don't on mine.
Yea I always had to manually set the timings in the bios, especially with fail dozer.
Posted on Reply
Add your own comment