Войти в систему

Home
    - Создать дневник
    - Написать в дневник
       - Подробный режим

LJ.Rossia.org
    - Новости сайта
    - Общие настройки
    - Sitemap
    - Оплата
    - ljr-fif

Редактировать...
    - Настройки
    - Список друзей
    - Дневник
    - Картинки
    - Пароль
    - Вид дневника

Сообщества

Настроить S2

Помощь
    - Забыли пароль?
    - FAQ
    - Тех. поддержка



Пишет AnandTech ([info]syn_anandtech)
@ 2013-03-26 02:28:00


Previous Entry  Add to memories!  Tell a Friend!  Next Entry
AMD Comments on GPU Stuttering, Offers Driver Roadmap & Perspective on Benchmarking

AMD remained curiously quiet as to exactly why its hardware and drivers were so adversely impacted by new FRAPS based GPU testing methods. While our own foray into evolving GPU testing will come later this week, we had the opportunity to sit down with AMD to understand exactly what’s been going on.

What follows is based on our meeting with some of AMD's graphics hardware and driver architects, where they went into depth in all of these issues. In the following pages we’ll get into a high-level explanation of how the Windows rendering pipeline works, why this leads to single-GPU issues, why this leads to multi-GPU issues, and what various tools can measure and see in the rendering process.



(Читать комментарии) (Добавить комментарий)