AMD's Radeon HD 6870 benchmarked? (updated more screens)

[Frodin]

EDIT: And why do i sense there would be tripled or quadrupled FUDs regarding ATi's bad driver, game support, etc, in the next few months or until there's a new rumour regarding nVidia's next gen card surfacing in the web.

Haha, yeah, I was kind of waiting for "but 20% faster, 30% less power consumption do not matter when ATI can´t write drivers worth s$%#".
I just hope these cards are not priced higher than 5xxx cards, rather that they replace them at more or less the same price point. Thinking about it, a second hand 5870 would probably serve me well enough.

[Xoulz]

pff come on, you know thats not how it works :P
especially in a tesselation geometry benchmarks pixels dont matter that much...

Are you saying the resolution doesn't matter, when dealing with tessilation..?

[Calmatory]

Are you saying the resolution doesn't matter, when dealing with tessilation..?

At least I am. Resolution (UNLESS IT CHANGES FIELD OF VIEW!) doesn't have ANYTHING to do with tesselation. The units which handle tesselation do not handle per-pixel operations, as far as I know, so there is no extra work for those units. The work remains the same regardless of the resolution.

However, obviously even with tesselation, the resolution has impact on the framerate, because there is a limit how many operations the ROPs can do, and how many operations the TMUs can do. With bigger resolution they need to do more. And they also need a bigger share of the memory bandwidth, too.

[Lanek]

Just learn to use the search....

Are you serious or are you only using Nvidia GPU?

[Eastcoasthandle]

how does this latest score relate against a 5800 series card ????

If those scores are true it will effectively place the 5870 as a mid range card.

[Lanek]

At least I am. Resolution (UNLESS IT CHANGES FIELD OF VIEW!) doesn't have ANYTHING to do with tesselation. The units which handle tesselation do not handle per-pixel operations, as far as I know, so there is no extra work for those units. The work remains the same regardless of the resolution.

However, obviously even with tesselation, the resolution has impact on the framerate, because there is a limit how many operations the ROPs can do, and how many operations the TMUs can do. With bigger resolution they need to do more. And they also need a bigger share of the memory bandwidth, too.

offcourse it will, tesselation impact on the anti-aliasing and anistrope filtering....... indirect lightning, and reflect............... It was not the case when ATI have release the API cause driver was optimised for it, but as Microsoft have choose a diferent path in DX11............. it's impact it a lot.......... For make it simple, tesselation don't kill the framerate, but the addtion of the filters uppon the surface tesselated do it.......

[Mechromancer]

you could always join gpugrid. they will have an ATi beta client out soon.

F@H said they would have an ATI specific client out soon too in 2006. If soon for GPUGrid is less than 4 years, I'm in!

[Dimitriman]

AMD needs to start getting their logos in a few games now.

[RPGWiZaRD]

AMD needs to start getting their logos in a few games now.

My thoughts exactly. Now would be a good time to do it, something corresponding to NVIDIA's "TWIMTBP". They've already had quite an upswing with HD 5xxx series when it comes to cooperating with game devs (well they were way ahead with DX11 support so no suprise), with HD 6xxx they could gain trust even easier.

[Florinmocanu]

Well, one thing saaya.

tesselation performance is not directly correlated with resolution when doing a unigine test, but.

Rendering is done per pixel. More pixels = more area to render, which means more shading/displacement/geometry etc....

I can tell you about normal CGI rendering, which shares a lot of similarities.

Displacement takes quite a lot of time to render and when the resolution is smaller, rendering goes faster. If you leave the same displacement and up the res, you increase linearly the rendering time, because the objects being displayed/rendered share a bigger pixel space. Displacement is done on screen, not for the whole scene, it would be crazy to do it like that.


So, resolution increase means also lower performance, even in Unigine.

[Metroid]

Crysis at 1920x1200 4AA: HD 6870 scored 43.5 FPS. The GTX 460 1024 SLI scored 40.0 FPS. Very Impressive if the results are true.

http://www.techpowerup.com/reviews/N...460_SLI/7.html

[deeperblue]

I can tell you about normal CGI rendering, which shares a lot of similarities.

Displacement takes quite a lot of time to render and when the resolution is smaller, rendering goes faster. If you leave the same displacement and up the res, you increase linearly the rendering time, because the objects being displayed/rendered share a bigger pixel space. Displacement is done on screen, not for the whole scene, it would be crazy to do it like that.

Well... CGI rendering is actually quite different from the graphics cards rendering pipeline.
Take a look at this:
http://i.msdn.microsoft.com/Ff569022...s,VS.85%29.png
From Input Assembler until after the Geometry Shader everything is done resolution independent! (as somebody mentioned assuming same aspect ratio) The Rasterizer and Pixel Shader are then operating on the actual pixel level of the current rendering target.

[sniper_sung]

It is said that the Unigine results are fake because the fonts are not consistent:



Source: http://www.chiphell.com/forum.php?mo...&fromuid=58492

[Jowy Atreides]

Umm yeah, it originates from here. They got the information from the other thread.

[Tha Last Meal]

Fake

[Florinmocanu]

Well... CGI rendering is actually quite different from the graphics cards rendering pipeline.
Take a look at this:
http://i.msdn.microsoft.com/Ff569022...s,VS.85%29.png
From Input Assembler until after the Geometry Shader everything is done resolution independent! (as somebody mentioned assuming same aspect ratio) The Rasterizer and Pixel Shader are then operating on the actual pixel level of the current rendering target.

Nope. In CGI effects are calculated resolution independent as well, but then to display them, it takes more time at higher resolution than lower one. Displacement is the best example for this, it is done usually with physical scale in mind (the amount the model is tessellated (1 polygon every 1 mm or 3 mm or 5etc..) determines how detailed the model will be after the displacement is done). So, even if i render at 640x480 or 1024x768, the displacement is done independently on the model.

But, doing displacement at 1024x768 usually gives linear increases in the time of rendering vs 640x480. That's why a lot of times i avoid using displacement, because it's a resource hog.

[madcho]

This is a bit amazing. The guy has a GPU and don't post any screenshot of the die ? ...

I think it's a fake too, but a well done one.

[deeperblue]

Nope. In CGI effects are calculated resolution independent as well, but then to display them, it takes more time at higher resolution than lower one. Displacement is the best example for this, it is done usually with physical scale in mind (the amount the model is tessellated (1 polygon every 1 mm or 3 mm or 5etc..) determines how detailed the model will be after the displacement is done). So, even if i render at 640x480 or 1024x768, the displacement is done independently on the model.

But, doing displacement at 1024x768 usually gives linear increases in the time of rendering vs 640x480. That's why a lot of times i avoid using displacement, because it's a resource hog.

And that's exactly the point.
The DX11/OpenGL tesselation we are talking about are spawning millions of new polygons in the middle of the pipeline - independent of the rendering resolution.

Your CGI renderer most likely is implementing displacement mapping in a sub-pixel displacement way without generating tons of micro-polygons like we have in the GPU pipeline - so the renderer is resolution dependent.

[Dami3n]

I don´t know if all the leaked numbers are fake, but real performance must be very good. Otherwise i don´t think that AMD would kill the Ati brand.

[kadozer]

I like the theory someone mentioned earlier in the thread. Why change it now? Let's hope its true and they deliver with the rumored performance for the 6 series.

[Iconyu]

I don´t know if all the leaked numbers are fake, but real performance must be very good. Otherwise i don´t think that AMD would kill the Ati brand.

Interesting theory, AMD won't have a flop for their first AMD GPU...

[davidkozat]

mmmhh Interesting am have been for the last 3 years an Nvidia user (not a fan fanatic despite the PIC lolz just prefer them so far) maybe this ATI cards shows some really potential and I switch over... Thanks for the thread screw the haters LOLz... Keep info coming... after all isn't Education one of the purposes of this forum??

[saaya]

Are you saying the resolution doesn't matter, when dealing with tessilation..?

im sure it does, but from what ive seen the difference is very very low...

especially when you go from 1920x1080 to 1920x1200, which is what the original point was...

Well, one thing saaya.

tesselation performance is not directly correlated with resolution when doing a unigine test, but.

Rendering is done per pixel. More pixels = more area to render, which means more shading/displacement/geometry etc....

I can tell you about normal CGI rendering, which shares a lot of similarities.

Displacement takes quite a lot of time to render and when the resolution is smaller, rendering goes faster. If you leave the same displacement and up the res, you increase linearly the rendering time, because the objects being displayed/rendered share a bigger pixel space. Displacement is done on screen, not for the whole scene, it would be crazy to do it like that.

So, resolution increase means also lower performance, even in Unigine.

thx for the details
but im sure you will agree that the difference between 1080 and 1200 is tiny

Fake

so its really fake then?

I don´t know if all the leaked numbers are fake, but real performance must be very good. Otherwise i don´t think that AMD would kill the Ati brand.

good point... but as long as cayman outperforms gf104 they own the highend with a dual cayman card, so... they dont necessarily have to kick 4ss to feel confident about the 6000 series... hmmm

[spursindonesia]

.............

so its really fake then?

good point... but as long as cayman outperforms gf104 they own the highend with a dual cayman card, so... they dont necessarily have to kick 4ss to feel confident about the 6000 series... hmmm

Saaya, if the new chips are not really fast enough over the current line ups, so like you've previously suggested, then why they have to bother R&D & creating this whole new family ? DX 11 strengthening can wait until 28 nm arrives, can't they ? We know in current games, Evergreen is more than good enough on average.

Evergreen while long in the tooth is holding the fort just fine, and since Evergreen fastest chip is actually smaller than nVidia's current best perf/watt/die size area performer, GF 104, should the supply constraint abated, ATi could easily engage a price war for market share expansion, if needed.

These new chips IMHO have to be considerably faster while adding efficiency in the process, i know, that's quite a feat should ATi successfully pull it all the way out, but i think they have the capability & room to be so. Then, a new generation tagline would be well deserved & justified.

Regards.

[Johnny87au]

is this real or fake? scores seem to be smashing single 480s.. if true then hell yer!