By: Vincent Diepeveen (diep.delete@this.xs4all.nl), April 21, 2011 2:06 am
Room: Moderated Discussions
EduardoS (no@spam.com) on 4/20/11 wrote:
---------------------------
>Vincent Diepeveen (diep@xs4all.nl) on 4/20/11 wrote:
>---------------------------
>>there's a mulhi and a mullo in opencl. both are different instructions.
>
>OpenCL? AMD ISA...
>
>Mullo is the traditional 32 bit integer multiplier, mulhi is used to perform 64
>bit integer multiplier and could be used for [0; 1[ fixed point numbers, but currently
>there is no way to use it this from OpenCL.
Sure there is. That's why there is 2 units now per each 4 pe's that can execute these instructions.
I'd not be amazed if they didn't improve the opencl compiler yet.
Yet your 'no way' is easy to prove wrong. Just look in opencl specs version 1.1, it lists there mulhi and mullo.
>>google for furmark and radeon 6990 it's eating 450+ watt.
>
>375W with the powercap at default position, 300W with it at -20% position and 450W
>with it at +20% position, FirePro cards are 150W or 225W, as Tesla cards, already
>waste too much words in this meanless discussion, power isn't directly related to reliability.
>
You're spreading a lot of desinformation; like so many here. What matters is how much those cards eat in total.
Pickup a random gamerssite:
http://www.geeks3d.com/20110303/amd-radeon-hd-6990-march-8-2011-3072sp-and-450w/
This report the guy writes is accurate. In furmark and gpgpu it eats 450+ watt, only during typical gaming it eats 375 watt.
Good gpgpu software uses all PE's, in games it's about being high clocked and a huge bandwidth to the RAM. That eats less watts than if you effectively use all PE's.
You're really off by a lot and very stubborn there. Google, there is so many gamerssite which measured this accurately.
Note that 450 watt is over 150 watt or so over the pci-e specs?
Just like you're total off for the 6990 you're also off by a few hundreds of watts for the Nvidia's.
---------------------------
>Vincent Diepeveen (diep@xs4all.nl) on 4/20/11 wrote:
>---------------------------
>>there's a mulhi and a mullo in opencl. both are different instructions.
>
>OpenCL? AMD ISA...
>
>Mullo is the traditional 32 bit integer multiplier, mulhi is used to perform 64
>bit integer multiplier and could be used for [0; 1[ fixed point numbers, but currently
>there is no way to use it this from OpenCL.
Sure there is. That's why there is 2 units now per each 4 pe's that can execute these instructions.
I'd not be amazed if they didn't improve the opencl compiler yet.
Yet your 'no way' is easy to prove wrong. Just look in opencl specs version 1.1, it lists there mulhi and mullo.
>>google for furmark and radeon 6990 it's eating 450+ watt.
>
>375W with the powercap at default position, 300W with it at -20% position and 450W
>with it at +20% position, FirePro cards are 150W or 225W, as Tesla cards, already
>waste too much words in this meanless discussion, power isn't directly related to reliability.
>
You're spreading a lot of desinformation; like so many here. What matters is how much those cards eat in total.
Pickup a random gamerssite:
http://www.geeks3d.com/20110303/amd-radeon-hd-6990-march-8-2011-3072sp-and-450w/
This report the guy writes is accurate. In furmark and gpgpu it eats 450+ watt, only during typical gaming it eats 375 watt.
Good gpgpu software uses all PE's, in games it's about being high clocked and a huge bandwidth to the RAM. That eats less watts than if you effectively use all PE's.
You're really off by a lot and very stubborn there. Google, there is so many gamerssite which measured this accurately.
Note that 450 watt is over 150 watt or so over the pci-e specs?
Just like you're total off for the 6990 you're also off by a few hundreds of watts for the Nvidia's.
Topic | Posted By | Date |
---|---|---|
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/11 11:55 PM |
Graph is not red-green colorblind friendly (NT) | RatherNotSay | 2011/04/12 03:51 AM |
Fixed | David Kanter | 2011/04/12 08:46 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | James | 2011/04/12 12:30 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 02:51 PM |
Try HD6450 or HD6850 | EduardoS | 2011/04/12 03:31 PM |
Try HD6450 or HD6850 | David Kanter | 2011/04/13 10:25 AM |
Try HD6450 or HD6850 | EduardoS | 2011/04/13 03:20 PM |
of cause | Moritz | 2011/04/14 08:03 AM |
of cause | EduardoS | 2011/04/14 01:55 PM |
Barts = 5D | Moritz | 2011/04/14 09:26 PM |
Barts = 5D | Antti-Ville Tuunainen | 2011/04/15 12:38 AM |
Limiting fixed function units | Moritz | 2011/04/15 04:28 AM |
Limiting fixed function units | Vincent Diepeveen | 2011/04/20 02:38 AM |
lack of detail | Moritz | 2011/04/20 09:24 AM |
lack of detail | EduardoS | 2011/04/20 11:45 AM |
gpgpu | Vincent Diepeveen | 2011/04/16 02:10 AM |
gpgpu | EduardoS | 2011/04/17 12:31 PM |
gpgpu | Groo | 2011/04/17 12:58 PM |
gpgpu | EduardoS | 2011/04/17 01:08 PM |
gpgpu | Ian Ameline | 2011/04/18 03:55 PM |
gpgpu | Ping-Che Chen | 2011/04/19 12:59 AM |
GPU numerical compliance | Sylvain Collange | 2011/04/19 11:38 AM |
GPU numerical compliance | Vincent Diepeveen | 2011/04/20 02:17 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 02:02 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 04:41 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 05:52 AM |
gpgpu and core counts | none | 2011/04/20 07:05 AM |
gpgpu and core counts | EduardoS | 2011/04/20 11:36 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 10:16 AM |
gpgpu and core counts | EduardoS | 2011/04/20 11:34 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 07:24 PM |
gpgpu and core counts | EduardoS | 2011/04/20 08:55 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 06:48 AM |
gpgpu and core counts | EduardoS | 2011/04/22 01:41 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/21 10:42 AM |
AMD Compute and Texture Fetch | Vincent Diepeveen | 2011/04/22 01:14 AM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 10:53 AM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 01:46 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 02:02 PM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 02:18 PM |
AMD Compute and Texture Fetch | anon | 2011/04/22 03:30 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 09:17 PM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 12:12 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 10:23 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/22 02:11 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 08:39 AM |
Keep the crazy politics out of this | Vincent Diepeveen | 2011/04/22 09:12 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 10:44 AM |
gpgpu and core counts | Jouni Osmala | 2011/04/22 11:06 AM |
gpgpu | EduardoS | 2011/04/20 11:59 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 12:37 PM |
gpgpu | EduardoS | 2011/04/20 05:27 PM |
gpgpu | Vincent Diepeveen | 2011/04/21 02:06 AM |
gpgpu | EduardoS | 2011/04/22 02:00 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | PiedPiper | 2011/04/12 10:05 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 10:42 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | MS | 2011/04/15 05:04 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/16 02:25 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/16 08:42 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Vincent Diepeveen | 2011/04/20 02:20 AM |
memory | Moritz | 2011/04/14 09:03 PM |
memory - more | Moritz | 2011/04/15 11:11 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/14 11:30 AM |