Jump to content

Fiery

Administrators
  • Posts

    11182
  • Joined

  • Last visited

  • Days Won

    475

Posts posted by Fiery

  1. Yes, it utilizes the general data crunching capabilities of modern GPUs rather than their ability to render high-resolution 3D images. When you "just" process a huge amount of data with the GPU, the whole video card is stressed in a different way than when running e.g. a 3D game. We picked the GPGPU way to let AIDA64 users stress their GPUs without the need to switch to full-screen mode.

  2. Thank you. Due to the fundamental difference between a full-screen 3D app and a GPGPU application (AIDA64 SST), the GPU won't be loaded or stressed the same way with those apps. On our test systems it took 15-30 minutes to make the video adapter heat up with GPGPU to the same levels that a full-screen 3D app could reach in a few minutes. It's definitely a slight issue, but since we generally recommend our users to run AIDA64 System Stability Test for at least a couple of hours, I don't think this is a show-stopper issue.

  3. 1) You can activate the DIMM temperature measurement in AIDA64 / main menu / File / Preferences / Stability. After altering that option you need to restart AIDA64.

    2) As for the HP ENVY EC access, I'm not entirely sure if it's relevant on your system. Based on the measured values in HWiNFO, the values seem to show a huge fluctuation. And that usually means the readings are invalid (bogus).

    Regards,

    Fiery

  4. DDR3-1600 is an out of spec (overclocked) memory grade on most chipsets, and our reference results database do not feature any overclocked results due to our internal policy. We may include a DDR3-1600 or DDR3-1866 system featuring an AMD FX-8150 processor -- when that CPU becomes widely available.

    As for Z68, it's not much different to the P67 which we already have in our reference database. We may add a Z68 system to the database, featuring a Celeron G440 CPU.

  5. As a first step, we've added Battery Voltage to the Computer / Sensor page of AIDA64, also to the hardware monitoring module (OSD Panel, Sidebar Gadget, SensorPanel, etc). Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

    http://www.aida64.co...14gcn7wyrhdzzip

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

    Let me know how it works. We'll also work on the UPS power readout, which apparently is specific to APC UPSes, hence it cannot be done via the standard Windows Smart Battery API...

  6. We've just made the new GPU stress testing feature public in the following AIDA64 beta release:

    http://www.aida64.co...14gcn7wyrhdzzip

    It can be used to put stress on one or more GPUs in the system, by utilizing the GPGPU computation capabilities of OpenCL API.

    A couple of things to note about this new feature:

    1) First of all, it is in a beta stage right now. We'd like to hear your feedbacks about it, and collect any improvement ideas. We will only roll out this new feature in an AIDA64 stable release in the first half of 2012. This feature will be disabled in any upcoming new stable releases of AIDA64 that will be rolled out in 2011.

    2) Even this first public beta is capable of putting computation threads on multiple GPUs; supports CrossFireX, SLI and AMD DualGraphics configurations; supports mixed GPU configurations (one ore more nVIDIA GPUs + one or more AMD GPUs) under Windows 7; and of course it supports AMD APUs (Llano, Brazos, Trinity) as well. Putting stress simultaneously on an APU and one ore more discrete GPUs is also supported. OpenCL-capable IGP chips and mobile GPUs are supported. Multi-GPU video cards (e.g. GeForce GTX 590 and Radeon HD 6990) are supported.

    3) Any OpenCL devices can be stressed, but right now it's not possible to select which devices to stress. Hence all GPU-type OpenCL devices that can be found in the system will be stressed simultaneously.

    4) CPU-type OpenCL devices are not supported. We don't plan to support them, since for CPU stressing we have our own solution, the usual 64-bit System Stability Test module.

    5) You can check the list of available OpenCL-capable devices on the Display / GPGPU page in AIDA64. All GPU-type devices listed there will be stressed by the AIDA64 System Stability Test.

    6) Due to the way GPGPU implementations work, stressing the GPU also puts stress on other system components, e.g. system memory, CPU caches, CPU cores, and PCI Express links. Hence it's normal to have considerable CPU utilization while running the GPU stress test, even when CPU and FPU tasks are not enabled on the System Stability Test interface.

    7) Due to OpenCL not being capable of providing a device utilization measurement, AIDA64 System Stability Test is not able to show the GPU load% while the stress test is running. It is however possible to check the GPU load in other places in AIDA64, e.g. on the Display / GPU page, or on the OSD Panel or SensorPanel.

    8) We currently have no plans about supporting other GPGPU layers (e.g. CUDA, Stream, Direct3D CS) for GPU stressing purposes.

    9) The current GPU stress module doesn't implement error-checking or results validation, hence any computation issues or glitches will not be detected or reported.

    10) On old nVIDIA MCP chips (e.g. MCP73) the current GPU stress test may not work properly. We suspect it is due to a ForceWare driver bug or improper OpenCL support in ForceWare drivers. We'll investigate this issue later this year.

    Please let us know what do you think about this new feature, and what improvements would you like to see about it.

    Thanks,

    Fiery

    • Like 1
  7. Thanks for the reply, think you missed this bit tho' ;)

    No, I haven't. I wrote above: "In the next AIDA64 beta we'll widen the bar limit fields to 6 characters." That will extend the maximum limit value to 999999 KB/sec.

    Noted another problem if you select multiple bars to modify, changing the frame colour doesn't work 'globally' you have to do it for each individual bar.

    We'll check that, thanks!

  8. In the next AIDA64 beta we'll widen the bar limit fields to 6 characters.

    As for the alignment, you can sort of do it now, although it's a bit tricky :) If you select Embedded as bar place, then:

    1) If you have both the value and unit enabled, then you can increase the width of the unit to move the text to the center of the bar (horizontally).

    2) If you only have the value enabled (and the unit disabled), then you can benefit from an irregular configuration of adjusting the total item width to a much lower value than the bar width. So if you have e.g. a 300-pixel wide bar, try to set the item width to 150 pixels only. It will effectively move the text to the center of the bar (horizontally).

    I know these aren't perfect solutions, but you may be able to attain a better SensorPanel layout before we can implement a more advanced alignment configuration.

    As for the new bar styles, we do have plans about them ;)

×
×
  • Create New...