Radeon 3100 IGP 

Released March, 2008
  • 344 MHz

From what we know, Crystal Well technology has been reserved for Intel's high-end GTS-based processors, so it is likely to only make an appearance on the most expensive Core i7 models.
by Tarun-Iyer (Apr, 2013)
Fuzdilla has also received reports that suggest that L1, L2, L3 and L4 memory will instead be "shared between the CPU and GPU.
by Tarun-Iyer (Apr, 2013)

Features Key features of the Radeon 3100 IGP

pixel rate Number of pixels a graphics card can render to the screen every second

Radeon 3100 IGP
1.38 GPixel/s
GeForce 210
1.9 GPixel/s
Radeon 3000 IGP
1.38 GPixel/s

texture rate Speed at which a graphics card can perform texture mapping

Radeon 3100 IGP
1.38 GTexel/s
GeForce 210
3.8 GTexel/s
Radeon 3000 IGP
1.38 GTexel/s

floating point performance How fast the gpu can crunch numbers

Radeon 3100 IGP
27.52 GFLOPS
GeForce 210
35.2 GFLOPS
Radeon 3000 IGP
27.52 GFLOPS

shading units Subcomponents of the gpu, these run in parallel to enable fast pixel shading

Radeon 3100 IGP
40

texture mapping units Built into each gpu, these resize and rotate bitmaps for texturing scenes

Radeon 3100 IGP
4

render output processors GPU commponents responsible for transform pixels as they flow between memory buffers

Radeon 3100 IGP
4

In The News From around the web

14
Apr

Report: 'Crystal Well' Haswell IGP to Have 64MB L4 Cache

by Tarun Iyer |
www.tomshardware.com
The "Crystal Well" variant of Intel's upcoming Haswell lineup reportedly features a 64 MB L4 cache dedicated for graphics.
According to a report published by Fuzdilla, the "Crystal Well" variant of Intel's Haswell range of processors will feature a massive 64 MB cache dedicated for graphics.

Specifications Full list of technical specs

gpu

GPU brand ATi
GPU name RS780C
Clock speed 344 MHz
Is dual GPU No
Reference card None

raw performance

Shading units 40
Texture mapping units 4
Render output processors 4
Pixel rate 1.38 GPixel/s
Texture rate 1.38 GTexel/s
Floating-point performance 27.52 GFLOPS
Report a correction

Comments

comments powered by Disqus