ap_cmdline_win_x86_SSE2_OpenCl_NV

I don't appear to have this, but rather one with ATI labels, I guess from the old card. Do I create one?

I have a CUDA 42 and a CUDA 50 file for mbcuda.cfg... should I modify both. What exactly does this modification do?

Your looking at the wrong file Mark

Its called mbcuda.cfg not cuda 42 or 50 orsse2opekcl but

mbcuda.cfg

ops scratch that he's talking about both files , if you don't have them the sse2 opencl for the nvida rerun Lunatics it should not upset any units you have just supend them for now

---

Hey Glenn,

He hasn't installed the lunatics yet which is why he doesn't see the ap_cmdline_win_x86_SSE2_OpenCl_NV

if he does then it will install that file as well as the generic mbcuda.cfg

Mark, you don't have to install Lunatics but it will help your output, just make sure to select cuda 50 when you do so. It's set by default to cuda 22 I think.

Zalster

---

Any risk to installing lunatics? Does it just effect Bionic or other processes as well?

I didn't see any FAN/GPU temp monitors in the NVIDIA Geforce experience package that comes with the driver. What do you guys use to monitor the GTX 750Ti?

I use Precision X from EVGA to control the fans on my 750Tis.

You can go to EVGA.com to download it

Some people use TThrottle, I looked at it once and couldn't figure it out, lol...

Lunatics only affect Seti and won't affect an other projects. ( I use it on all my computers) You will need to adjust the setting in the created app_info.xml once it installs inorder to get 2 work units per card.

If you want to use it, there is a sticky thread at the top of the Number Crunching forum. Be sure to get v43.b

Only click on the nvidia options not the ati ones.

---

Any risk to installing lunatics? Does it just effect Bionic or other processes as well?

The only thing that the Lunatics installer does is to back up the old SETI program files, and place new files in the SETI@Home project subfolder. It's designed so that any existing SETI work cached or in progress on the machine is preserved (with one warning to avoid having in-progress AP work with the stock v7.00 CPU application). All it does to BOINC is to stop it running, and restart it afterwards, and no BOINC projects except SETI are affected in any way.

You will need to adjust the setting in the created app_info.xml once it installs inorder to get 2 work units per card.

For several versions now, the advice has been to leave the generated app_info.xml file well alone, and run a version of BOINC which allows GPU usage to be controlled via app_config.xml

The installer is designed to leave existing app_config.xml files untouched during installation, so that those customisations are preserved through updates.

I avoided telling him about the app_config as then we bring up the discussion on how to create the XML file.

---

I've created the app_config file, that's how I am running 2 WUs.

what about appinfo.xml after he installs lunatics ? , you can't pull out now spill all you know Zalster so he doesn't stuff it up .:-)

---

Then you are good to go if you want to install Lunatics

---

what about appinfo.xml after he installs lunatics ? , you can't pull out now spill all you know Zalster so he doesn't stuff it up .:-)

LOL, that would be entire blog in itself...........

---

I installed Lunatics and did the two edits you recommended Zalster. Not yet sure about the actuals, but the estimated times went up... is this normal?

I installed Lunatics and did the two edits you recommended Zalster. Not yet sure about the actuals, but the estimated times went up... is this normal?

Running 2 WUs at a time will take longer to crunch them than running one at a time. However, you will actually process more WUs per hour running 2 at a time than one, so your RAC will (eventually) increase.

---

Grant
Darwin NT

I just looked to see if any MB have the new setting. So far I haven't seen any change. So I'll wait a bit and recheck.

As per Grant..above :)

---

Its odd though, actual times seem fine, but estimated times seem to have gone way up since making these changes. It isn't taking anywhere near the estimated times to complete the tasks, its taking way less.

Remember those are just estimates, it takes some time for results to get recorded then the times will come down

---

This is the actual file, let me know if I missed something:

;;; This configuration file is for optional control of Cuda Multibeam x41zc
;;; Currently, the available options are for
;;; application process priority control (without external tools), and
;;; per gpu priority control (useful for multiple Cuda GPU systems)
[mbcuda]
;;;;; Global applications settings, to apply to all Cuda devices
;;; You can uncomment the processpriority line below, by removing the ';', to engage machine global priority control of x41x
;;; possible options are 'belownormal' (which is the default), 'normal', 'abovenormal', or 'high'
;;; For dedicated crunching machines, 'abovenormal' is recommended
;;; raising global application priorities above the default
;;; may have system dependant usability effects, and can have positive or negative effects on overall throughput
;processpriority = abovenormal
;;; Pulsefinding: Advanced options for long pulsefinds (affect display usability & long kernel runs)
;;; defaults are conservative.
;;; WARNING: Excessive values may induce display lag, driver timeout & recovery, or errors.
;;; pulsefinding blocks per multiprocessor (1-16), default is 1 for Pre-Fermi, 4 for Fermi or newer GPUs
;pfblockspersm = 8
;;; pulsefinding maximum periods per kernel launch (1-1000), default is 100, as per 6.09
;pfperiodsperlaunch = 200

;[bus1slot0]
;;; Optional GPU specifc control (requires Cuda 3.2 or newer app), example
;processpriority = normal
;pfblockspersm = 16
;pfperiodsperlaunch = 400

;;; Optional GPU specifc control (requires Cuda 3.2 or newer app), example
;processpriority = normal
;pfblockspersm = 16
;pfperiodsperlaunch = 400

Remove the bolded items.

I'm not see anonymous under your computer, you said you install Lunatics?

---

I did.

;processpriority = normal
;pfblockspersm = 16
;pfperiodsperlaunch = 400

You need to uncomment these lines to make them active. Remove the semicolon in front of each line and the re-read the config files in Boinc Manager.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)