| | | | | | |

Xeon Bronze 3206R vs Celeron E3300


Description
The 3206R is based on Cascade Lake architecture while the E3300 is based on Core.

Using the multithread performance as a reference, the 3206R gets a score of 103.8 k points while the E3300 gets 22.2 k points.

Summarizing, the 3206R is 4.7 times faster than the E3300 . To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
50657
1067a
Core
Cascade Lake-SP
Wolfdale
Architecture
Base frecuency
1.9 GHz
2.5 GHz
Socket
LGA 3647-0
LGA 775
Cores/Threads
8/8
2/2
TDP
85 W
65 W
Cache L1 (d+i)
8x32+8x32 kB
32+32 kB
Cache L2
8x1024 kB
1024 kB
Cache L3
11264 kB
0 kB
Date
February 2020
August 2009
Mean monothread perf.
31.52k points
12.94k points
Mean multithread perf.
216.02k points
24.6k points

Non-optimized benchmark
The benchmark in Mode 0 (FPU) measures cpu performance with non-optimized software. It uses the basic µinstructions from the i386 architecture with the i387 floating point unit. This mode is compatible with all CPUs so it's practical to compare very different CPUs
Monothread
3206R
E3300
Test#1 (Integers)
1.97k
2.29k (x1.17)
Test#2 (FP)
8.15k
5.87k (x0.72)
Test#3 (Generic, ZIP)
2.37k
2.49k (x1.05)
Test#1 (Memory)
4.84k
1.01k (x0.21)
TOTAL
17.32k
11.66k (x0.67)

Multithread

3206R

E3300
Test#1 (Integers)
15.73k
4.57k (x0.29)
Test#2 (FP)
64.78k
11.66k (x0.18)
Test#3 (Generic, ZIP)
18.06k
4.89k (x0.27)
Test#1 (Memory)
5.21k
1.04k (x0.2)
TOTAL
103.77k
22.16k (x0.21)

Performance/W
3206R
E3300
Test#1 (Integers)
185 points/W
70 points/W
Test#2 (FP)
762 points/W
179 points/W
Test#3 (Generic, ZIP)
212 points/W
75 points/W
Test#1 (Memory)
61 points/W
16 points/W
TOTAL
1221 points/W
341 points/W

Performance/GHz
3206R
E3300
Test#1 (Integers)
1035 points/GHz
916 points/GHz
Test#2 (FP)
4287 points/GHz
2347 points/GHz
Test#3 (Generic, ZIP)
1246 points/GHz
995 points/GHz
Test#1 (Memory)
2547 points/GHz
405 points/GHz
TOTAL
9115 points/GHz
4663 points/GHz

Monothread performance graph
Monothread performance graphics gives the performance vs time. They are useful to measure the time it takes to the CPU to reach the maximum performance.

Usually, CPU's performance will be steady during these tests but if it has a slow frequency strategy, the first samples will show a lower score.


Test#1 (Integers) [points vs time]

grafica bm.hardlimit.com


Test#2 (FP) [points vs time]

grafica bm.hardlimit.com


Test#3 (Generic, ZIP) [points vs time]

grafica bm.hardlimit.com


Test#1 (Memory) [points vs time]

grafica bm.hardlimit.com

Multithread performance graph
Multithread graphs measure the performance against a heavy load during certain time.

If CPU's TDP doesn't limit the frequency and the machine is properly cooled, performance should remain steady vs time. Otherwise, the performance score will oscillate or decrease over time.


Test#1 (Integers) [points vs time]

grafica bm.hardlimit.com


Test#2 (FP) [points vs time]

grafica bm.hardlimit.com


Test#3 (Generic, ZIP) [points vs time]

grafica bm.hardlimit.com


Test#1 (Memory) [points vs time]

grafica bm.hardlimit.com

Hardlimit Benchmark Central - Ver. 3.11.4