AMD "Lucienne" Silicon to Power Certain Ryzen 5000 Series APUs

[btarunr]

There's been much chatter in the social media about a new piece of AMD APU silicon, codenamed "Lucienne." It's being rumored that "Lucienne" is a refresh of the current-generation "Renoir" silicon, and is an APU with eight "Zen 2" CPU cores and eight "Vega" NGCUs. One of the first SKUs based on the die is the Ryzen 7 5700U, which surfaced on the AoTS benchmark database.

The 5700U is possibly a 15 W ultra-portable processor, and according to the AoTS benchmark screenshot, it comes with an 8-core/16-thread CPU (the 4700U is 8-core/8-thread). The addition of SMT helps the 5700U shore up much of its performance lead over the 4700U. It also turns out that the Ryzen 5000 will see two APU dies driving AMD's product-stack, with "Lucienne" powering the Ryzen 5 5500U and Ryzen 7 5700U; while the newer "Cezanne" die, which introduces "Zen 3" CPU cores, powers the Ryzen 5 5600U and the Ryzen 7 5800U.



View at TechPowerUp Main Site

 

[Camm]

Because that isn't going to be confusing as fuck.

 

[T1beriu]

"Lucienne," (possibly after the French singer Lucienne Boyer)

*Facepalm*. It's actually Lucienne Bisson, a painter (remember all other CPU codenames are painters, right?), the illegitimate daughter of Renoir. *ding ding ding*

 

[Proedros]

Renoir "refresh".

Lucienne Bisson - Wikipedia

en.wikipedia.org

Edit .... T1beriu, you beat me to it

 

[sutyi]

Makes no sense.

The whole point of going 5000 series with ZEN3 on desktop was to bring the same base architecture to the same nomenclature, as the mobile segment was "lagging" behind.

 

[sergionography]

AMD decides to name the new Zen3 CPUs as the 5000 series.

Fans and the press: AMD finally responded to our complains and decided to name the new CPUs as 5000 series to avoid confusing us!

AMD: hold my beer

 

[Proedros]

AMD decides to name the new Zen3 CPUs as the 5000 series.

Fans and the press: AMD finally responded to our complains and decided to name the new CPUs as 5000 series to avoid confusing us!

AMD: hold my beer

6000 it is..... /s

edit: Could be that Google ordered them?

Comes AMD’s new and still secret “Lucienne” APU exclusively as 8-core only for Google? OPN and first data leaked! | igor´sLAB

With the CPUs and APUs, AMD obviously makes it like a highly infectious virus, you mutate quickly and attack Intel’s general health on all fronts. There is no other way to look at it…

www.igorslab.de

 

[theGryphon]

*Facepalm*. It's actually Lucienne Bisson, a painter (remember all other CPU codenames are painters, right?), the illegitimate daughter of Renoir. *ding ding ding*

Illegitimate surely checks out in this occasion.

 

[john_]

Makes no sense.

The whole point of going 5000 series with ZEN3 on desktop was to bring the same base architecture to the same nomenclature, as the mobile segment was "lagging" behind.

Maybe 5000 series will have both Zen 2 and Zen 3 models on the desktop and later on the mobile. Zen 2 is good enough to give the idea to AMD to rebrand certain models. For example 3700X and 3800X where looking very close and no reason to have both of them. On the other hand 5700X could be a rebrand of 3800XT and 5800X a new Zen 3 model.

 

[LemmingOverlord]

*Facepalm*. It's actually Lucienne Bisson, a painter (remember all other CPU codenames are painters, right?), the illegitimate daughter of Renoir. *ding ding ding*

Was gonna trashtalk the article for this, but you stopped me. Thank you.

 

[medi01]

Because that isn't going to be confusing as fuck.

That what they said about Xbox One X vs Xbox Series X.

https://twitter.com/x/status/1308497697775562752

 

[Caring1]

*Facepalm*. It's actually Lucienne Bisson, a painter (remember all other CPU codenames are painters, right?), the illegitimate daughter of Renoir. *ding ding ding*

Want an e-peen point?
Who cares, it's a code name.

 

[T1beriu]

Want an e-peen point?

I want competent TPU writers.

 

[Chrispy_]

I knew they wouldn't be able to resist using the 5000-series for Zen2 rehashes. Their marketing depart has always been comprised of idiots.

 

[milewski1015]

Maybe 5000 series will have both Zen 2 and Zen 3 models on the desktop

Is that not what they've been doing? The APUs generally utilize the previous architecture while keeping the same generational identifier:

2200G/2400G: Zen
2600/2700X/etc. Zen+

3200G/3400G: Zen+
3600/3700X/etc: Zen 2

So maybe:

5200G/5400G: Zen 2
5600/5700X/etc: Zen 3

 

[Chrispy_]

Is that not what they've been doing? The APUs generally utilize the previous architecture while keeping the same generational identifier:

2200G/2400G: Zen
2600/2700X/etc. Zen+

3200G/3400G: Zen+
3600/3700X/etc: Zen 2

So maybe:

5200G/5400G: Zen 2
5600/5700X/etc: Zen 3

That's almost a pattern, but then there's no explanation for skipping the 4000-series naming for Zen3 Vermeer.

 

[Kapone33]

I swear the next 6 months will be mind blowing for PC anything!

 

[seronx]

Or, all Zen3 and RDNA2 products in the mainline are the 6000-series.

Examples:
Ryzen 9 6950X = 16-core Vermeer
Ryzen 7 6700X = 8-core Vermeer

RX 6900XT = 80CU Sienna Cichlid
RX 6700XT = 40CU Navy Flounder
RX 6500XT = 24CU Dimgrey Cavefish

Ryzen 9 6900U = 8-core Rembrandt+16-CU RDNA2. (H-model => 24 CUs + Navy Flounder) <== DDR5 DIMMs
Ryzen 7 6700U = 8-core Cezanne+8-CU Vega-H. (H-model => Paired with Dimgrey Cavefish) <== DDR4 DIMMs

Ex2:
Enthusiast: 4000-series/Van Gogh(RDNA2-Navy Flounder), 5000-series/Mero(RDNA2-Navi Flounder), 6000-series/Rembrandt(RDNA2-Sienna Cichlid)
Mainstream-Performance: 4000-series/Renoir(GCN-Vega), 5000-series/Lucienne(GCN-Vega), 6000-series/Cezanne(CDNA-VegaH)

Products being skipped are strike-through. APU Navi Flounder = One graphics pipe, APU Sienna Cichlid = Two graphics pipes.

 

[john_]

Is that not what they've been doing? The APUs generally utilize the previous architecture while keeping the same generational identifier:

2200G/2400G: Zen
2600/2700X/etc. Zen+

3200G/3400G: Zen+
3600/3700X/etc: Zen 2

So maybe:

5200G/5400G: Zen 2
5600/5700X/etc: Zen 3

I don't have APUs in my mind. I did gave a specific example.

 

[milewski1015]

I don't have APUs in my mind. I did gave a specific example.

I saw it. I don't think that's something AMD would go for. The naming is already confusing enough for people in regards to the APUs, let alone having two 8 core 16 thread CPUs in the same 5000 series but one on a different architecture than the other for example. And we all know how everybody feel about refreshes: cough Intel cough

 

[john_]

I saw it. I don't think that's something AMD would go for. The naming is already confusing enough for people in regards to the APUs, let alone having two 8 core 16 thread CPUs in the same 5000 series but one on a different architecture than the other for example. And we all know how everybody feel about refreshes: cough Intel cough

If a confusing naming can sell more hardware to people who will never really care about the architecture of the chip they bought, then they will gladly do it. They did it in the past. Remember the RX 300 series cards.

 

[milewski1015]

If a confusing naming can sell more hardware to people who will never really care about the architecture of the chip they bought, then they will gladly do it. They did it in the past. Remember the RX 300 series cards.

They were before I got into PC hardware back in early 2018 but I imagine they support your prediction. It all remains to be seen I guess.

 

[Turmania]

I'm pretty sure these tech companies have a proper reason a methodbto this naming madness. But, I fail to see it.

 

[mechtech]

Naming conventions meaning anything for cpus/gpus have been messed forever now. It would be nice if they could always be logical, but in the end I don't really care if they call it
supercalifragilisticexpialidocious a, b, and c, as long as its good performance for the $.

 

[LabRat 891]

Ah, back to the A64 days where a single generation had different core code names, sometimes on different nodes, and with different cache configurations and architectural iterations. As long as the models are named and marketed according to performance, I see nothing wrong with this.