Page 3 of 17 FirstFirst 1234513 ... LastLast
Results 21 to 30 of 164

Thread: Benchmarks Of AMD's Newest Gallium3D Driver

  1. #21

    Default

    Quote Originally Posted by pingufunkybeat View Post
    Are you sure that this is enough?

    AFAIK, you need to patch the driver manually to disable vsync.
    I've talked it over with Alex before and he said vblank_mode 0 should work fine.

  2. #22
    Join Date
    Jun 2009
    Posts
    2,927

    Default

    It makes sense, since at least one result was higher than 60fps.

    Still, I think that the more recent driver versions with all the latest patches should perform considerably better.

  3. #23
    Join Date
    Nov 2007
    Posts
    1,024

    Default

    Quote Originally Posted by airlied View Post
    Its about 100 developers working full time.

    Dave.
    A slightly more useful answer might include what the specific bottlenecks are that you'd put the first 5 of those 100 developers on. Pretend I was a GPU driver development rockstar, I was hired by AMD full-time, you were my boss, and you could tell me to work on anything you wanted in any particular order: what would you want me to do first?

  4. #24
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    911

    Default

    Quote Originally Posted by Michael View Post
    I've talked it over with Alex before and he said vblank_mode 0 should work fine.
    I tried and it doesn't. My HD3870 runs Openarena at 100fps @2560x1600 w/ Very High Quality (with mesa classic, gallium should be even better). How can an HD4870 do only 47fps with a lower resolution? .-.

  5. #25
    Join Date
    Dec 2009
    Posts
    134

    Default

    It seems the Gallium3d is starving the HW. 80% of the time HD is just idling?
    Any one is monitoring the GPU command queue?

  6. #26
    Join Date
    Dec 2009
    Posts
    338

    Default

    Quote Originally Posted by elanthis View Post
    A slightly more useful answer might include what the specific bottlenecks are that you'd put the first 5 of those 100 developers on. Pretend I was a GPU driver development rockstar, I was hired by AMD full-time, you were my boss, and you could tell me to work on anything you wanted in any particular order: what would you want me to do first?
    Maybe you should read Jerome's letter and the rest in that thread?

  7. #27
    Join Date
    Oct 2008
    Posts
    3,078

    Default

    Quote Originally Posted by darkbasic View Post
    I tried and it doesn't. My HD3870 runs Openarena at 100fps @2560x1600 w/ Very High Quality (with mesa classic, gallium should be even better). How can an HD4870 do only 47fps with a lower resolution? .-.
    The r600g driver is mostly CPU limited right now, i think. Maybe your cpu is just faster?

    Quote Originally Posted by The Article
    tested on a system with an Intel Core i5 750 quad-core CPU clocked at 2.67GHz,

  8. #28
    Join Date
    Nov 2007
    Posts
    1,024

    Default

    Quote Originally Posted by HokTar View Post
    Maybe you should read Jerome's letter and the rest in that thread?
    Indeed, that's a good read, and excellent work on the part of jglisse. Thanks.

  9. #29
    Join Date
    Oct 2009
    Location
    .ca
    Posts
    402

    Default

    Quote Originally Posted by HokTar View Post
    Maybe you should read Jerome's letter and the rest in that thread?
    Interesting link, thanks.

  10. #30
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,411

    Default

    Quote Originally Posted by elanthis View Post
    A slightly more useful answer might include what the specific bottlenecks are that you'd put the first 5 of those 100 developers on. Pretend I was a GPU driver development rockstar, I was hired by AMD full-time, you were my boss, and you could tell me to work on anything you wanted in any particular order: what would you want me to do first?
    The first task would be to find the bottlenecks. With a graphics driver that is usually a pretty significant task on its own. The graphics driver and the GPU are largely decoupled by a large command buffer and periodic synchronization events so your normal "run the app and see where the time goes" approach doesn't work so well.

    It's more like "run the app, see where the time goes, develop a theory, talk to a few people, if they don't totally demolish your theory then write a bunch of code, see if it makes that app go faster, be happy because it does, test your change on other apps, get PO'ed because your change makes the other apps run slower, repeat".

    Finding bottlenecks would be a good job for the first 5 developers.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •