Temperature is currently at 68°C. I can not get it low. This card will power itself down when reached 109°C. So as long as I can keep it below 80°C it should be okay. Ambient temperature will only increase as the season gradually warms.

---

Greetings from TJ

I give up.

---

BOINC <<--- credit whores, pedants, alien hunters

I just replaced my two 680s with two 780Tis. Only on my first run with the new cards, but so far the times seem better.

Running 334.89:
SANTI_MAR GPU utilization 72% @ 1137MHz
NOELIA_FXA GPU utilization 79% @ 1124MHz

I always have one card in my case that boosts just a bit higher than the other.

Looking at the current progress and comparing it against my runs on the 680s, it looks like the NOELIA task will complete about 2 hours faster, and the the SANTI task will complete about 1.5 hours faster.

---

I just replaced my two 680s with two 780Tis. Only on my first run with the new cards, but so far the times seem better.

Running 334.89:
SANTI_MAR GPU utilization 72% @ 1137MHz
NOELIA_FXA GPU utilization 79% @ 1124MHz

I always have one card in my case that boosts just a bit higher than the other.

Looking at the current progress and comparing it against my runs on the 680s, it looks like the NOELIA task will complete about 2 hours faster, and the the SANTI task will complete about 1.5 hours faster.

Which model Matt?

EVGA GTX 780Ti 03G-P4-2883-KR.

---

Completed times on first WUs:

NOELIA - 18110s
SANTI - 20764s

This is a great improvement over the GTX 680s, however I think I'm now running into one of the issues mentioned above in this thread. After the card running NOELIA finished it started on a SANTI and downclocked from 1124MHz to 980MHz. The other card stayed at it's boost speed of 1137MHz after completing a SANTI and beginning a NOELIA.

I have Nvidia preferences set for maximum performance. Temps are good - the card at 1137MHz is at 70C and the card at 980MHz is at 60C. Utilization for NOELIA/SANTI is still the same.

Edit: Hmm, may have jumped the gun a bit. Rebooted and now back to 1124/1137. Maybe the Nvidia preferences needed a reboot to take effect? I'll have to check again after these WUs finish.

Edit 2: ...and now it has downclocked to 980 again - the same card both times. It is the card I'm running my displays from. Never had an issue with the 680s downclocking.

---

Edit: Hmm, may have jumped the gun a bit. Rebooted and now back to 1124/1137. Maybe the Nvidia preferences needed a reboot to take effect? I'll have to check again after these WUs finish.

Edit 2: ...and now it has downclocked to 980 again - the same card both times. It is the card I'm running my displays from. Never had an issue with the 680s downclocking.

I bet if you were to run an app that tracks and records the temperature and clock speeds over time for a few tasks and then graphed that data you would see that the clocks stay up until the temp goes above a certain cutoff temp then the clock drops until the temp drops back down below that cutoff temp. I bet your card that is downclocking is doing so because the temp rises above 70C. That seems to be the temp where mine downclock.

I've found that if I set the fanspeed to say 60% the temp might be at say 65C and it will stay at 65C for many minutes. If I go away for an hour and then peak at the temperature I find sometimes it has risen by 6 degrees to 71C and I also find it has downclocked.

I think the temp rises for 2 reasons (maybe more):

1) the temperature of the air going into the case rises for some reason (the furnace kicks in or someone closes a window, for example)

2) the simulation reaches a hard spot that works the GPU harder

The fix is to recurve the fanspeed or run software that monitors the GPU temp and increases the fanspeed when the temp rises and decreases the fanspeed when the temp falls. The software allows you to set a target temperature which is the temp at which you want the GPU to run. It works like a thermostat.

---

BOINC <<--- credit whores, pedants, alien hunters

Temperature is very model, brand and even individual card depending. My primary EVGA GTX660 runs at 75°C steady with radial fan at maximum speed which is 75% for this card and will not become any cooler. But is steady at 940MHz for 6 days without booting. Some WU's, especially Santi's can down clock the card a bit but it will go up again if that WU finishes.

---

Greetings from TJ

Temperature is very model, brand and even individual card depending.

I agree and that is part of the problem with tweaking GPUs to get top performance. There are so many variables to deal with. I know I always say "We need a script to solve this" but I think if we had a script to collect temperature, clocks, % usage and various other data every second (maybe 2 seconds) for the entire length of tasks and then graph that data we would get a much better understanding of what is happening. I can do that for Linux hosts and have a possible way of doing it for Windows hosts. Storing the data and graphing it is easy but I don't have code for reading the data from the GPU on Windows yet, just Linux.

---

BOINC <<--- credit whores, pedants, alien hunters

Why not use HWiNFO and its Sensor logging ?

Why not use HWiNFO and its Sensor logging ?

I had never heard of HWiNFo for Windows until now, thanks. It looks like it might have everything one needs. If it logs the data we would want for GPUgrid tasks and is capable of composing the kind of graphs that would be useful to GPUgrid users then it would be great. Anybody doing it so far?

Python exposes many of the NVIDIA driver API calls and there are graphing apps (GNU plot) that runs on Windows as well as Linux. Python runs on Windows too. Using that API via Linux one could write one app that runs on Windows and Linux that logs precisely the data we want and produces exactly the graphs we want. That's easy with Python because it can also use the BOINC API to access task names and other useful data BOINC generates and exposes via its API. That would allow you to log data and associate its graph with a task name, driver version, OS, BOINC configuration and hundreds of other types of info/data that HWiNFO might not be able to access or graph. It might or it might not, I have no idea as I've never used it.



graphs it, apparently. TIf WiIt might be worth looking into.

---

BOINC <<--- credit whores, pedants, alien hunters

I have installed it and used it, but the readings differ with other programs that read all sort of system information but especially temperatures differ. I have started a thread about temperature readings and it seems everyone has it own preference for a reading program.

---

Greetings from TJ

Since your objective is to keep the GPU temperature below a limit then believe the application that reports the highest temperature. If you can keep the temp reported by that app below the limit then you can be quite certain it actually is below the limit.[/quote]

---

BOINC <<--- credit whores, pedants, alien hunters

I think there's a lot of users logging data using HWiNFO and it can directly draw graphs too. Here's one example, though for AMD, but NV is similar:

I have installed it and used it, but the readings differ with other programs that read all sort of system information but especially temperatures differ. I have started a thread about temperature readings and it seems everyone has it own preference for a reading program.

Which exact temperatures differ, can you please post which sensor is it and which value? Also what other tools do you use, which show different values ?
I believe most tools use NVAPI to read NV GPU temperatures on later families and so HWiNFO does, so I'm really wondering that there are differences.
Let me know about any issues and I'll look at that, since I'm the author of HWiNFO ;-)

BTW, I have already contacted the author of BoincTasks about an integration with HWiNFO and he thinks it's a good idea, but is currently very busy. But I think this might be implemented sometime.. would be definitively interesting to see all sorts of sensor information from HWiNFO via BoincTasks.

BTW, I have already contacted the author of BoincTasks about an integration with HWiNFO and he thinks it's a good idea, but is currently very busy. But I think this might be implemented sometime.. would be definitively interesting to see all sorts of sensor information from HWiNFO via BoincTasks.

You're the author, excellent :-) Integration with BoincTasks would be very handy for all BOINC volunteers. BT runs on Linux too under Wine so integration would be cross platform compatible... perfect. I'm moving this "log data and graph it" thing to lowest priority on my "would like to code it" list and I intend to try HWiNFO for Linux ASAP. No, wait!! The hwinfo package for Linux is a different package! Or did you author it for Linux as well? If not then I would be interested in collaborating with you to make a Linux version of your HWiNFO so users can have the same experience on both platforms. First I have other stuff to clear off my plate but perhaps in a couple months...

---

BOINC <<--- credit whores, pedants, alien hunters

You're the author, excellent :-) Integration with BoincTasks would be very handy for all BOINC volunteers. BT runs on Linux too under Wine so integration would be cross platform compatible... perfect. I'm moving this "log data and graph it" thing to lowest priority on my "would like to code it" list and I intend to try HWiNFO for Linux ASAP. No, wait!! The hwinfo package for Linux is a different package! Or did you author it for Linux as well? If not then I would be interested in collaborating with you to make a Linux version of your HWiNFO so users can have the same experience on both platforms. First I have other stuff to clear off my plate but perhaps in a couple months...

The HWiNFO I do is for Windows (and DOS) only. The hwinfo on Linux is a completely different thing. Porting my HWiNFO to Linux would be a really huge effort. Though I think about that sometimes, I don't believe this is going to happen in near future.

I was thinking more like I write the Linux version and make it look and feel like the Windows version as much as possible. The collaboration part would involve very little work from you. But that's a topic for a different discussion in a different thread some time in the future. PM if interested or I might PM you about it in a month or so. Right now I'm just discovering the power of GKrellM for Linux. I overlooked it for a while but today the light went on and I realized just how much it can do. It's awesome and will be included in Crunchuntu.

---

BOINC <<--- credit whores, pedants, alien hunters

I was thinking more like I write the Linux version and make it look and feel like the Windows version as much as possible. The collaboration part would involve very little work from you. But that's a topic for a different discussion in a different thread some time in the future. PM if interested or I might PM you about it in a month or so. Right now I'm just discovering the power of GKrellM for Linux. I overlooked it for a while but today the light went on and I realized just how much it can do. It's awesome and will be included in Crunchuntu.

I'm not sure how you meant that, but sure, let's move this discussion out of this thread. You can PM me, or better send direct e-mail (you can find mine in HWiNFO)...

Under Windows, NVSMI shows the GPU temps and drivers for all cards, and more info for Titans, Quadro's and Teslas.
It's found in C:\Program Files\NVIDIA Corporation\NVSMI (nvidia-smi.exe) and can be accessed from a command prompt in Windows.
I think it might also be found in Linux, but I haven't checked.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Under Windows, NVSMI shows the GPU temps and drivers for all cards, and more info for Titans, Quadro's and Teslas.
It's found in C:\Program Files\NVIDIA Corporation\NVSMI (nvidia-smi.exe) and can be accessed from a command prompt in Windows.
I think it might also be found in Linux, but I haven't checked.

There is no nvidia-smi in Linux. For Linux they ship the nvidia-settings app which, when run from command line with no args, starts the nvidi-settings GUI. If run with args (and there are a million possible args, just do 'man nvidia-settings' to read the manual) it exposes the driver API, very powerful. Or you can just click on the nvidia-settings icon to open the GUI which allows setting fan speeds if you've set coolbits in xorg.conf. It also gives a load of info and allows other tweaks such performance profile which can be used to increase performance. What nvidia-settings does not do is allow to set a target temperature and for that reason it is not the app it could be so I give it 4 out of 5 stars.

I use calls to nvidia-settings extensively in my gpu_d script to get temp readings and to adjust fanspeed up and down for the purpose of maintaining the user specified target temp.

---

BOINC <<--- credit whores, pedants, alien hunters