Notebookcheck Logo
, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

AMD Ryzen 5 3580U vs AMD Ryzen 3 PRO 3300U

AMD Ryzen 5 3580U

► remove from comparison AMD R5 3580U

Der AMD Ryzen 5 3580U (Microsoft Surface Edition) ist ein Mobilprozessor für schlanke Notebooks. Der SoC beinhaltet 4 Zen+ Kerne (Quad-Core CPU). Im Vergleich zum Vorgänger Ryzen 5 2500U wurde der Herstellungsprozess leicht verbessert (14 auf 12nm) welcher höhere Taktraten bei gleichem Stromverbrauch erlaubt. Weiters wurden minimale Verbesserungen bei der Microarchitektur vorgenommen (etwa 3% höhere IPC, Leistung pro Takt). Dadurch soll die neue Generation 8% schneller sein als die Vorgängermodelle (laut AMD). Im Vergleich zum ähnlichen Ryzen 5 3500U, bietet der Ryzen 5 3580U eine schnellere GPU mit 9 statt 8 CUs (576 Shader).

Die Prozessorleistung sollte daher sehr vergleichbar zu einem durchschnittlichen Ryzen 5 3500U sein.

Die Features bleiben bei den neuen APUs der Picasso Serie vergleichbar zur Vorgängergeneration, wodurch wir auf unseren Raven Ridge APU Artikel verweisen können.

AMD Ryzen 3 PRO 3300U

► remove from comparison AMD R3 PRO 3300U

Der AMD Ryzen 3 PRO 3300U ist ein Mobilprozessor für schlanke Business-Notebooks. Der SoC beinhaltet 4 Zen+ Kerne (Quad-Core CPU) welche von 2,1 - 3,5 GHz getaktet werden. Die APU unterstützt jedoch kein SMT / Hyperthreading und dadurch können nur 4 Threads gleichzeitig abgearbeitet werden. Im Vergleich zum Consumer Ryzen 3 3300U bietet die PRO-Version zusätzliche Management, Sicherheitsfunktionen und längere Garantiezeiten / Verfügbarkeit. Im Vergleich zum Vorgänger Ryzen 3 PRO 2300U wurde der Herstellungsprozess leicht verbessert (14 auf 12nm) welcher höhere Taktraten bei gleichem Stromverbrauch erlaubt. Weiters wurden minimale Verbesserungen bei der Microarchitektur vorgenommen (etwa 3% höhere IPC, Leistung pro Takt). Dadurch soll die neue Generation 8% schneller sein als die Vorgängermodelle (laut AMD).

Die integrierte Radeon RX Vega 6 bietet 6 CUs (384 Shader) mit bis zu 1200 MHz.

Die Features bleiben bei den neuen APUs der Picasso Serie vergleichbar zur Vorgängergeneration, wodurch wir auf unseren Raven Ridge APU Artikel verweisen können.

ModelAMD Ryzen 5 3580UAMD Ryzen 3 PRO 3300U
SeriesAMD Picasso (Ryzen 3000 APU)AMD Picasso (Ryzen 3000 APU)
CodenameZen+Zen+
Serie: Picasso (Ryzen 3000 APU) Zen+
AMD Ryzen 7 3780U compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 7 3750H compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 7 3700U compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 7 PRO 3700U compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 5 3550H compare2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 3500U compare2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 PRO 3500U compare2.1 - 3.7 GHz4 / 84 MB
» AMD Ryzen 5 3580U2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 3450U compare2.1 - 3.5 GHz4 / 84 MB
AMD Ryzen 3 3350U compare2.1 - 3.5 GHz4 / 44 MB
AMD Ryzen 3 3300U compare2.1 - 3.5 GHz4 / 44 MB
AMD Ryzen 3 PRO 3300U2.1 - 3.5 GHz4 / 44 MB
AMD Ryzen 7 3780U compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 7 3750H compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 7 3700U compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 7 PRO 3700U compare2.3 - 4 GHz4 / 84 MB
AMD Ryzen 5 3550H compare2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 3500U compare2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 PRO 3500U compare2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 3580U2.1 - 3.7 GHz4 / 84 MB
AMD Ryzen 5 3450U compare2.1 - 3.5 GHz4 / 84 MB
AMD Ryzen 3 3350U compare2.1 - 3.5 GHz4 / 44 MB
AMD Ryzen 3 3300U compare2.1 - 3.5 GHz4 / 44 MB
» AMD Ryzen 3 PRO 3300U2.1 - 3.5 GHz4 / 44 MB
Clock2100 - 3700 MHz2100 - 3500 MHz
L1 Cache384 KB384 KB
L2 Cache2 MB2 MB
L3 Cache4 MB4 MB
Cores / Threads4 / 84 / 4
TDP15 Watt15 Watt
Transistors4500 Million4500 Million
Technology12 nm12 nm
SocketAM4AM4
FeaturesXFR, FMA3, SSE 4.2, AVX2, SMTXFR, FMA3, SSE 4.2, AVX2, SMT
iGPUAMD Radeon RX Vega 9 ( - 1300 MHz)AMD Radeon RX Vega 6 (Ryzen 2000/3000) ( - 1200 MHz)
Architecturex86x86
Announced
ManufacturerAMD Picasso (Ryzen 3000 APU) R3 PRO 3300U

Benchmarks

Performance Rating - CB R15 + R20 + 7-Zip + X265 + Blender + 3DM11 CPU - R5 3580U
33.1 pt (39%)
Cinebench R20 - Cinebench R20 CPU (Single Core)
352 Points (45%)
Cinebench R20 - Cinebench R20 CPU (Multi Core)
1549 Points (7%)
Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
693 Points (7%)
03570105140175210245280315350385420455490525560595630665Tooltip
481 Points (5%)
0255075100125150175200225250275300325350375400425450475Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
139 Points (48%)
126 Points (43%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
7.8 Points (14%)
5.5 Points (10%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
1.7 Points (47%)
1.4 Points (41%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
4525 Points (40%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
18307 Points (25%)
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
22657 Points (20%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
6410 Points (39%)
wPrime 2.10 - wPrime 2.0 1024m *
274.7 s (3%)
wPrime 2.10 - wPrime 2.0 32m *
7.2 s (1%)
WinRAR - WinRAR 4.0
2924 Points (17%)
7-Zip 18.03 - 7-Zip 18.03 Multli Thread 4 runs
15209 MIPS (11%)
7-Zip 18.03 - 7-Zip 18.03 Single Thread 4 runs
3572 MIPS (51%)
X264 HD Benchmark 4.0 - x264 Pass 2
40.1 fps (18%)
X264 HD Benchmark 4.0 - x264 Pass 1
135.3 fps (37%)
HWBOT x265 Benchmark v2.2 - HWBOT x265 4k Preset
4.1 fps (9%)
TrueCrypt - TrueCrypt Serpent
0.4 GB/s (14%)
TrueCrypt - TrueCrypt Twofish
0.6 GB/s (13%)
TrueCrypt - TrueCrypt AES
3.5 GB/s (13%)
Blender 2.79 - Blender 2.79 BMW27 CPU *
710 Seconds (5%)
3DMark 06 - CPU - 3DMark 06 - CPU
5545 Points (12%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
12 s (3%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
27.2 s (1%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
694 s (3%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
21501 Points (22%)
3DMark 11 - 3DM11 Performance Physics
6856 Points (24%)
5408 Points (19%)
3DMark - 3DMark Ice Storm Physics
47473 Points (31%)
3DMark - 3DMark Ice Storm Extreme Physics
48287 Points (40%)
3DMark - 3DMark Ice Storm Unlimited Physics
52082 Points (44%)
3DMark - 3DMark Cloud Gate Physics
6687 Points (17%)
4646 Points (12%)
3DMark - 3DMark Fire Strike Standard Physics
9805 Points (24%)
6596 Points (16%)
3DMark - 3DMark Time Spy CPU
2898 Points (16%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
3908 Points (60%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
11829 Points (29%)
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Single-Core
900 Points (44%)
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
2990 Points (10%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
1243 ms (1%)
Octane V2 - Octane V2 Total Score
28517 Points (29%)
Power Consumption - Prime95 Power Consumption - external Monitor *
41.1 Watt (7%)
Power Consumption - Cinebench R15 Multi Power Consumption - external Monitor *
40 Watt (11%)
Power Consumption - Cinebench R15 Multi Power Efficiency - external Monitor
17.3 Points per Watt (20%)

Average Benchmarks AMD Ryzen 5 3580U → 100% n=7

Average Benchmarks AMD Ryzen 3 PRO 3300U → 76% n=7

- Bereich der Benchmarkergebnisse für diese Grafikkarte
- Durchschnittliche Benchmarkergebnisse für diese Grafikkarte
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 28. 21:52:04

#0 checking url part for id 11514 +0s ... 0s

#1 checking url part for id 11336 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Sat, 28 May 2022 13:12:34 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.006s ... 0.007s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.008s

#6 linkCache_getLink no uid found +0.003s ... 0.011s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#14 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#16 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#18 composed specs +0s ... 0.011s

#19 did output specs +0s ... 0.011s

#20 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.013s

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#22 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.015s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.015s

#24 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.015s

#25 getting avg benchmarks for device 11514 +0.002s ... 0.017s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.017s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.017s

#28 got single benchmarks 11514 +0.007s ... 0.025s

#29 getting avg benchmarks for device 11336 +0s ... 0.025s

#30 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.025s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.026s

#32 got single benchmarks 11336 +0.005s ... 0.031s

#33 got avg benchmarks for devices +0s ... 0.031s

#34 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.031s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#36 linkCache_getLink using $NBC_LINKCACHE +0.012s ... 0.043s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#74 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#79 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#82 min, max, avg, median took s +0s ... 0.06s

#83 linkCache_getLink using $NBC_LINKCACHE +0.031s ... 0.091s

#84 return log +0.004s ... 0.095s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Prozessor Vergleich - Head 2 Head
Autor: Redaktion,  8.09.2017 (Update: 19.05.2020)