• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

RTX 2080 memory bandwidth issue

Oh, good. For a moment there I was worried we ran out of people that can tell others what they need to do :p

W1zz does not have to listen to me, us, to do anything. He can keep GPU-Z as is.
These were mere suggestions, and with lack of said features GPU-Z might risk of irrelevance among media and users.
 
Last edited:
2.12.0 released with fix for GDDR6 bandwidth. I'll think about the other proposed changes for next version
 
W1zz does not have to listen to me, us, to do anything. He can keep GPU-Z as is.
These were mere suggestions, and with lack of said features GPU-Z might risk of irrelevance among media and users.
Yeah, ok. I was just thinking, what you posted is so obvious, it's probably on their list already ;)
 
2.12.0 released with fix for GDDR6 bandwidth. I'll think about the other proposed changes for next version
Much appreciated. all around. :)

As it stands, the difference between what NVIDIA reports as Pixel Fillrate GT/s and GPUz is confusing and a bit concerning. I would imagine that the software should report what the whitepaper does unless its some odd dubious method. Considering these cards will all hit base boost clock+ in 99% of situations, it doesn't make sense, to me, to list it based off the base clock and going against whitepapers. I don't understand why the deviation...

RE: Tensor/RT cores, those should also be listed was suggested when they came out. A suggestion on how to implement them without jamming up the first page of GPUz.... perhaps only have it on RTX cards. The software can load up those fields only when it detects an RTX card. If the software can figure out NV/AMD and put up their avatar, it should be able to scrape and figure out if its an RTX and add the fields for those cores and values. This way, if a GPUz user has an RTX card, it will know and use the proper fields, but older NV GPUs and AMD GPUs won't get those fields as it does not have the hardware.

Anyway, thanks for the time you spend supporting the software. Your work is appreciated. :)
 
^^^ If space is a concern, those can go into a separate tab.
 
That's the thing, it was brought up in another thread that maybe it can go in the advanced tab, but, I don't see why it should be buried if its a standard piece of hardware in the card...which is what that first page of GPUz lists. That said, I do understand the need for a clean interface and not jamming it up when so few people have these cards with those features in hand, hence the suggestion to make the software aware and only display those fields with applicable cards. Then once this takes off and makes its way to AMD cards, it can be a permanent fixture.
 
Yes, it wouldn't be the most intuitive thing, that much is clear. That's why I suggested it would be used only if it is to solve the space problem.
It doesn't need to be an "advanced" tab, but maybe a "Graphics Card (continued)" tab instead?
 
Back
Top