FYI to all Nvidia Crunches out there... Clock speed Problems

Forums › Cruncher's Corner

Tex1954
Tex1954
Joined: 15 Mar 11
Posts: 28
Credit: 775707141
RAC: 618050
25 May 2011 13:09:28 UTC
Topic 195804
(moderation:
    )

    There is an ongoing problem with CUDA tasks and the Clock Rates being dropped in Nvidia I've written it up and the problem is with Vista and Win7 both.

    What happens, is the clock rate gets dropped to conserve power/heat etc. and never returns to high speed again. This always happens with DUAL Nvidia cards installed and seems only magic prevents it from happening on it's own most of the time. Doesn't matter what power settings are set, performance mode seems to help, but not totally correct it. Snoozing or Suspending tasks is a 95% guarantee the clocks with drop and never regain full speed again.

    I've informed Nvidia tech support and the forums.

    http://forums.nvidia.com/index.php?s=9f29a996e0ac9d6ea44a506f6631f805&showtopic=200414&pid=1237460&st=0entry1237460

    8-)

    Tex1954

    Richard Haselgrove
    Richard Haselgrove
    Joined: 10 Dec 05
    Posts: 2143
    Credit: 2951620253
    RAC: 692627

    FYI to all Nvidia Crunches out there... Clock speed Problems

    25 May 2011 13:52:24 UTC
    Message 105483
    (moderation:
      )

      As I've just posted in reply to your identical post at SETI:

      Quote:

      This problem has recently been drawn to the attention of the SETI CUDA developers, and is in the process of being reported onwards to other CUDA-enabled BOINC projects. It seems to be related specifically to the release of nVidia drivers which will support the forthcoming v4 release of the CUDA run-time support files. The central BOINC library code isn't yet fully compatible with CUDA v4: the problem has been overcome with test programs, and should go away with the next round of application releases.

      Unfortunately, v3 and earlier nVidia drivers aren't available for the very latest generation of nVidia cards, but if you have a card which can run with nVidia driver 266.58, that should avoid the problem.


      @ Bernd:

      It's been isolated to a CUDA task exit handling problem in the BOINC API library code. Eric Korpela has a copy of the proposed (and tested) solution for evaluation, and is considering checking it in following testing and evaluation. I can put you in touch with the developer concerned, or pass messages, if you wish.

      Tex1954
      Tex1954
      Joined: 15 Mar 11
      Posts: 28
      Credit: 775707141
      RAC: 618050

      Thanks for the good work and

      26 May 2011 18:33:38 UTC
      Message 105484 in response to message 105483
      (moderation:
        )

        Thanks for the good work and the heads up!

        8-)

        Tex1954

        Bernd Machenschalk
        Bernd Machenschalk
        Moderator
        Administrator
        Joined: 15 Oct 04
        Posts: 4312
        Credit: 250230131
        RAC: 35930

        Thanks. I pointed Oliver to

        27 May 2011 14:20:39 UTC
        Message 105485 in response to message 105483
        (moderation:
          )

          Thanks. I pointed Oliver to this thread.

          BM

          BM

          Speedy
          Speedy
          Joined: 11 Aug 05
          Posts: 39
          Credit: 23376889
          RAC: 76

          Is it worth updating to

          17 Jun 2011 4:56:14 UTC
          Message 105486
          (moderation:
            )

            Is it worth updating to GeForce 275.33 Driver? Released 11/06/01 Dose this release fix the down clocking issues?

            Thanks for advice in advance

            Richard Haselgrove
            Richard Haselgrove
            Joined: 10 Dec 05
            Posts: 2143
            Credit: 2951620253
            RAC: 692627

            RE: Is it worth updating to

            17 Jun 2011 5:43:10 UTC
            Message 105487 in response to message 105486
            (moderation:
              )

              Quote:
              Is it worth updating to GeForce 275.33 Driver? Released 11/06/01 Dose this release fix the down clocking issues?


              No, it's the 275.33 driver which causes the downclocking issues - or more strictly, reveals the bug in the BOINC API which causes them.

              Although the API bug has been fixed (in theory), this project hasn't re-compiled and re-issued the applications to take advantage of it yet (and nor has any other BOINC project that I'm aware of).

              FrankHagen
              FrankHagen
              Joined: 13 Feb 08
              Posts: 102
              Credit: 272200
              RAC: 0

              RE: Although the API bug

              17 Jun 2011 15:40:25 UTC
              Message 105488 in response to message 105487
              (moderation:
                )

                Quote:
                Although the API bug has been fixed (in theory), this project hasn't re-compiled and re-issued the applications to take advantage of it yet (and nor has any other BOINC project that I'm aware of).

                well - it would be nice if this could be done at least.

                and probably giving CUDA 4.0 a try then..

                Comment viewing options

                Select your preferred way to display the comments and click "Save settings" to activate your changes.

                Forums › Cruncher's Corner