Language

AMD E1-2100

Table of Contents
  1. Introduction
  2. Specifications
  3. Conclusion
  4. Comments

Introduction

The AMD E1-2100 is a mobile processor of the E1 (Kabini) generation, launched on May 23rd, 2013. It comes with 2 cores and 2 threads, clocked at 1000 MHz and consumes up to 9 Watts.

Specifications

Codename
Kabini
Generation
E1 (Kabini)
Market
Mobile
Release Date
May 23rd, 2013
Process Size
32 nm
TDP
9 W
Socket
AMD Socket FT3
Frequency
1000 MHz
Turbo Frequency
Cores
2
Threads
2
Cache L1
128K (per core)
Cache L2
512K (per core)
Integrated Graphics
Radeon HD 8210
Memory Support
DDR3
ECC Memory
No
PCI-Express
Features
3DNow!, AES, AMD-V, AMD64, AVX, BMI1, CnQ, F16C, MMX, NX bit, SSE, SSE2, SSE3, SSE4.1, SSE4.2, SSE4A

Benchmarks

Geekbench 5 Multi-thread
GeekBench is a cross-platform benchmarking utility. It runs a series of tests that simulate real world tasks. GeekBench multi-thread utilizes all cores, this makes it suitable for benchmarking servers.
188
Geekbench 5 Single-thread
GeekBench is a cross-platform benchmarking utility. It runs a series of tests that simulate real world tasks. GeekBench single-thread utilizes only one thread. The majority of applications (MS Word, web browsers, games) rarely utilize more than one thread at a time which makes this test suitable for measuring typical workloads.
106

Conclusion

Global performance
4%
Global multi-thread performance
1%
Global single-thread performance
6%
Mobile performance
5%
Mobile multi-thread performance
2%
Mobile single-thread performance
7%
Multi-thread performance — shows multi-thread performance compared to the fastest processor.
Single-thread performance — shows single-thread performance compared to the fastest processor.
Global performance — shows performance compared to the fastest processor.
Desktop performance — shows performance compared to the fastest desktop processor.
Mobile performance — shows performance compared to the fastest mobile processor.
Server performance — shows performance compared to the fastest server processor.
Comments