Lunatics Windows Installer v0.43b Maintenance Release

Message boards : Number crunching : Lunatics Windows Installer v0.43b Maintenance Release
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Richard HaselgroveProject Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 11516
Credit: 106,054,701
RAC: 70,705
United Kingdom
Message 1704229 - Posted: 23 Jul 2015, 11:17:26 UTC

Lunatics are pleased to announce the availability of the v0.43b installer in the Lunatics main download area and mirror sites.
Please take care you use the right installer (32/64 bit) for your system.

Should you have any questions or problems - ask! Post in this thread or open a new one.

New in this installer:
---------------------
Added support for Astropulse v7 on all platforms.
Maintenance release v0.43a: Updated all AP GPU applications from r2721 to r2737, addressing a system memory usage problem on tasks with high signal counts.

Maintenance release v0.43b:
Removed support for obsolete AP v6 tasks.
Restored support for AP (v7) on older ATI cards with updated Brook application.
Further updates to OpenCL applications (all GPU types).
Fixed OpenCL build failure with NVidia Release 352 drivers.
Added installation support (cache protection) for stock v7.07 tasks.

No changes to CPU or CUDA applications.


How to use the installer:
------------------------
For the CPU applications, you need to know what your CPU supports. Either check the Boinc startup messages or check with CPU-Z downloadable from http://www.cpuid.com
Tick or untick CPU AP and MB applications as desired.
Tick ATI (OpenCL) AP or MB if/as desired.
Tick NVidia (OpenCL) AP or CUDA MB if/as desired.
Tick Intel (OpenCL) AP or MB if/as desired.
More details further down.

NB We use default values throughout the app_info.xml. If you have previously installed optimised applications and manually edited app_info.xml (e.g. <count> for multithreading GPUs, <flops>, <cmdline> for ATI) you WILL lose those edits on running the installer and have to redo them. You may wish to make a note of them.
You will also lose all other manual edits to app_info.xml such as beta applications.

You are strongly recommended to use a version of BOINC which supports app_config.xml files. These can be used to manage the number of tasks running on each GPU more simply than by editing app_info.xml, and will NOT be removed by re-running this or subsequent installers. If you have previously used an app_config file for Astropulse, you may want to add a similar section for Astropulse_v7.

Known issues - general:
----------------------
The AP v7 CPU applications can all run on BOINC 7 installations running in service mode.

Be careful when upgrading if you have already pre-installed optimised AP v7 applications from individual pre-release build packs. Some of these packs deploy version numbers derived from Beta testing, and they are not guaranteed to match the Main project release values. This installer follows the application version numbers and plan classes displayed on http://setiathome.berkeley.edu/apps.php - if yours differ, set NNT and drain your cache before proceeding.

TAKE SPECIAL CARE when upgrading from the stock 7.00 Astropulse CPU application. The intermediate checkpoint files have a non-standard format, and the Lunatics applications can't resume a part-computed task. Either set NNT and wait until the current task(s) have finished - may be a long wait - or abort tasks if they haven't progressed very far. This only applies to v7.00 tasks which have commenced processing - v7.03 (sse or sse2) tasks are safe to upgrade while in progress, and all unstarted tasks are safe.

BOINC v7 installations are not able to run any GPU applications in service mode, and the installer will now bypass GPU application pages on machines which cannot run GPU applications because of this restriction.

The installer is supposed to shut down the BOINC client whilst leaving the Manager running - noticable from the red 'disconnected' dot in the tray. After finishing the BOINC client should restart and the red dot vanish when the Manager reconnects. This may take a few minutes. On some systems however this fails to work. Please ensure BOINC has restarted.
Advanced users only: If you know you are going to edit app_info.xml, it may be easier to shutdown and restart BOINC manually, so you can get the changes into app_info.xml before the restart.

Some users reported that installer v0.41 failed to assemble a complete app_info.xml file from the aistub files supplied with each application. We have switched to using a 'grep' application (supplied) called from a slightly modified 'aimergeg.cmd' script to help avoid this problem. The original aimerge script is also present for people who are used to using it.


CPU MB apps - AKv8c r2549 (unchanged)

If you have any doubt at all about what instruction sets your CPU supports, download CPU-Z from http://www.cpuid.com/softwares/cpu-z.html

We have now incorporated a 3rd party CPU feature detection tool into the installer. Unsupported applications will be greyed out, and the installer will pre-select recommended application versions for your CPU.


CPU AP v7 app - r2672/2692/2696/2703 depending on optimisation level.

A 32-bit AVX build is offered for the first time - at the SSE3 level, the installer will choose between AMD and Intel builds automatically (there wasn't space for an extra manual choice).


NVidia GPU (CUDA) app - x41zc

For details please see the separate ReadMe_x41zc.txt.

Rule of thumb selection guide:
Cuda 2.3: PreFermi - NOT to be used on Fermi/Kepler/Maxwell
Cuda 3.2: mixed systems
Cuda 4.2: Fermi
Cuda 5.0: Kepler/Maxwell
If you have run stock and have established APR you can also pick the fastest app from there.
For compatible cards see http://developer.nvidia.com/cuda-gpus
Should run on all NVidia CUDA cards with at least 512MiB video RAM. Actual free memory required is in the region of 200-235MB, depending on driver, OS flavour and CUDA variant. The code will scale up if more memory is available. Running on a 256MiB card is just possible, but you will have to free up as much VRAM as possible, e.g. by disabling Aero.
Used video RAM can be checked with GPU-Z downloadable from
http://www.techpowerup.com/downloads/2244/techpowerup-gpu-z-v0-7-1/
Watch closely on GPU-Z and in BOINC manager if the application finds enough memory.
Symptoms of insufficient memory are
- in BOINC manager: tasks start up and run a few seconds then go to 'waiting
to run' and the next task tries to start
- on GPU-Z: the sensor for memory shows used VRAM ramping up and almost
immediately dropping again.
Depending on BOINC version your tasks will either error out with 'too many exits' or get stuck in an infinite loop.
If you don't have enough memory, set BOINC to NNT, abort tasks and uninstall the CUDA application by rerunning the installer with CUDA MB UNticked. If in doubt ask for help on NC: http://setiathome.berkeley.edu/forum_forum.php?id=10
To multithread on Fermi/Kepler cards, find all instances of <count>1</count> in app_info.xml and decrease to 0.5 or 0.3 to run two or three tasks in parallel.
Again, if you are uncertain of how to do this correctly, ask on the above mentioned forum. 'Your mileage may vary' - it depends on your specific system which count will give the highest throughput.
Full release notes and history in separate readme.


NVidia (OpenCL) AP v7 app - updated to r2887

Please see separate ReadMe_AstroPulse_OpenCL_NV.txt for details.
Reserving one CPU core per GPU card will improve performance.

Warning - the NVidia 340.52 driver (released 29 July 2014) causes invalid results on legacy compute capability 1.1, 1.2 and 1.3 cards. This application will - deliberately - NOT run on such cards: it will alternate between displaying a warning message in BOINC Manager and apparently 'running', but will make no progress and eventually error out. If you have an old card (8000 series, 9000 series, or 2xx series), either exclude it from crunching AP, or downgrade to an older driver.

Alternatively, the 'hotfix' 341.44 driver (released 24 February 2015) can be used if available - not all operating system versions are supported.



ATI (OpenCL) MB app - updated to r2929

Please see separate ReadMe_MultiBeam_OpenCL_ATI.txt for details, especially on driver requirements.
Reserving one CPU core per GPU card will improve performance.
We offer the MB application in two different variants, depending on card:
plain - for most HD4xxx owners and those with HD5xxx, HD6xxx cards and
HD7xxx cards who suffer from driver incompatibilities.
HD5 - for most if not all owners of HD5xxx, HD6xxx and HD7xxx GPUs.

ATI (OpenCL) AP v7 app - updated to r2742
ATI (Brook) AP app - updated to r2904

Please see separate ReadMe_AstroPulse_OpenCL_ATI.txt or ReadMe_AstroPulse_Brook.txt for details, especially on driver requirements.
Reserving one CPU core per GPU card will improve performance.

For cards without OpenCL support (from HD2xxxx on) use the 'hybrid' r2904 Astropulse application. NB this is a combined CPU/GPU application and will only use the GPU for some of the calculations, while doing the rest on a CPU core. Minimum driver version Catalyst 9.x.

The Hybrid AP application uses about 80% of a CPU core and does only about 20% of the calculations on the GPU. Parameters have been choosen to reflect this usage. However present BOINC can not reserve '0.8' of a CPU core and therefore reserves none. This means your CPUs will be overcommitted and runtimes and DCF (if applicable) will suffer. You do increase the overall output though.

HD2xxx cards requiring Brook (Hybrid) applications are once again supported by Lunatics for Astropulse v7.


Intel (OpenCL) applications for both MB and AP v7 (updated to r2929/r2742)

These are now offered by Lunatics. Please note the supported iGPU models, and observe the minimum OpenCL and driver versions, shown on the selection page. Intel CPUs offering plain "HD graphics" may be able to run these applications, with a suitable driver, but have not been exhaustively tested. Please verify that tasks run on these devices are validating consistently before allowing them to run unattended.

You MUST update your Intel driver if BOINC reports the OpenCL version as 1.1
The applications may appear to run without updating the driver, but the results will not be valid and you will have wasted your computing power.

Visit https://downloadcenter.intel.com/ if you require an updated graphics driver for your iGPU. Note that you will require a driver for a 3rd. or 4th. generation Intel 'core' CPU with the appropriately numbered HD or Iris graphics support.

Many people have reported problems getting Intel's automated update and installation tools to work, but their manual installation instructions (requiring the download of the '.zip' driver package) appear to work on systems which reject the automated tools. A copy of Intel's ReadMe file for driver installation will be placed in the Lunatics docs folder for reference if you select either of the iGPU applications.


This time the thanks go to Joe (Josef W. Segur) for the optimised CPU apps, to Raistmer (with additional input from Urs Echternacht) for OpenCL apps and to Jason (jason_gee) for CUDA apps.
Thanks guys. There would be no need for an optimised app installer if there weren't optimised apps in the first place!

We would also like to take this opportunity to thank our active alpha testers
(in no particular order and apologies to anybody we've forgotten):
Claggy, arkayn and Mike.


The Lunatics Installer team AD MMXV
ID: 1704229 · Report as offensive
Richard HaselgroveProject Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 11516
Credit: 106,054,701
RAC: 70,705
United Kingdom
Message 1704232 - Posted: 23 Jul 2015, 11:20:20 UTC

Just for clarity: this is not a required update: you can continue using the previous v0.43 or v0.43a releases if they are working correctly on your hardware. But this release will tidy up some rough edges, like the warnings about unrecognised Astropulse v6 applications in the message log.
ID: 1704232 · Report as offensive
Profile MikeProject Donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 30589
Credit: 57,537,239
RAC: 30,500
Germany
Message 1704239 - Posted: 23 Jul 2015, 12:19:06 UTC
Last modified: 23 Jul 2015, 12:42:55 UTC

For ATI GPU users r_2929 included in the 0.43b release is more mature and has more tuning options like oclfft_tune and other options.

Please read the read me file.

Here is link to some config examples.

It contains comand_line.txt example of tune params and a device specific xml file as well as a modified aistub.

Config file
With each crime and every kindness we birth our future.
ID: 1704239 · Report as offensive
Profile Chris SCrowdfunding Project Donor
Volunteer tester
Avatar

Send message
Joined: 19 Nov 00
Posts: 40026
Credit: 34,679,461
RAC: 62,911
United Kingdom
Message 1704257 - Posted: 23 Jul 2015, 13:34:29 UTC

Many thanks Mike and Richard, your work is always appreciated.
ID: 1704257 · Report as offensive
Richard HaselgroveProject Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 11516
Credit: 106,054,701
RAC: 70,705
United Kingdom
Message 1704273 - Posted: 23 Jul 2015, 14:37:10 UTC

For those that like to check such things, here are the file checksums for the v0.43b installers.

==================================================
Full Path         : C:\Lunatics_build_v43b\Lunatics_Win32_v0.43b_setup.exe
Modified Time     : 23/07/2015 10:30:54
File Size         : 21,106,314
CRC32             : E29E1772
MD5               : C64F12E67146AEB05F6CBAEE5454065B
SHA-256           : 9DFD57DF0B9C994AF72A8705516473B6208D9A00D4556023900A97ED6DC09A26
==================================================

==================================================
Full Path         : C:\Lunatics_build_v43b\Lunatics_Win64_v0.43b_setup.exe
Modified Time     : 23/07/2015 10:27:06
File Size         : 21,876,000
CRC32             : 8C892F28
MD5               : 184740DA9766CB1D1906D85400A31EAC
SHA-256           : 1C7F7108A5D6E5390ED2BCF3202DC68FFD7B2BF92CC813DF1A8602A88E2033A1
==================================================
ID: 1704273 · Report as offensive
Profile TimeLord04
Volunteer tester
Avatar

Send message
Joined: 9 Mar 06
Posts: 18641
Credit: 9,776,343
RAC: 260
United States
Message 1704287 - Posted: 23 Jul 2015, 15:29:06 UTC
Last modified: 23 Jul 2015, 15:46:46 UTC

Now that 0.43b fixes the 352.x Driver issues for NVIDIA; will I see any difference in Drivers from 337.88??? (Faster crunching, or whatever...???) Or, should I stick with 337.88 on both my crunchers.

Prometheus: GTX-750 TI SC, Driver 337.88, Win 7 Pro x64.

Exeter: GTX-760, Driver 337.88, Win XP Pro x64.


What benefits are there to updating the Drivers to 352.x??? (Neither system does gaming that require the latest Drivers.)


TL
TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
ID: 1704287 · Report as offensive
Profile TimeLord04
Volunteer tester
Avatar

Send message
Joined: 9 Mar 06
Posts: 18641
Credit: 9,776,343
RAC: 260
United States
Message 1704349 - Posted: 23 Jul 2015, 19:06:44 UTC

I've just downloaded Drivers from 347.88 to 353.30 for Win XP Pro x64 for Exeter, and the same for Win 7 Pro x64 for Prometheus.

For AP WUs, is OpenCL 1.2 faster at crunching than 1.1??? What will the latest Drivers do in combination with Lunatics 0.43b on my two systems???


TL
TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
ID: 1704349 · Report as offensive
Richard HaselgroveProject Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 11516
Credit: 106,054,701
RAC: 70,705
United Kingdom
Message 1704350 - Posted: 23 Jul 2015, 19:15:47 UTC - in response to Message 1704349.  

I'm not the timekeeper for these apps - I just pack 'em and drop 'em. Anybody got any comparative stats for the Time Lord?
ID: 1704350 · Report as offensive
Profile Blurf
Volunteer tester

Send message
Joined: 2 Sep 06
Posts: 8864
Credit: 11,354,558
RAC: 5,345
United States
Message 1704357 - Posted: 23 Jul 2015, 19:32:50 UTC

Been looking forward to this update. Thx Richard!


ID: 1704357 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7471
Credit: 91,021,900
RAC: 11,399
Australia
Message 1704360 - Posted: 23 Jul 2015, 20:03:04 UTC - in response to Message 1704349.  

In general, the underlying technology (including drivers) moves from old-school methods toward new techniques. That can either work better (hopefully in most cases) or choke horribly if everything isn't 100% yet. (ymmv, lol)
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1704360 · Report as offensive
Profile MikeProject Donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 30589
Credit: 57,537,239
RAC: 30,500
Germany
Message 1704362 - Posted: 23 Jul 2015, 20:08:24 UTC - in response to Message 1704349.  

I've just downloaded Drivers from 347.88 to 353.30 for Win XP Pro x64 for Exeter, and the same for Win 7 Pro x64 for Prometheus.

For AP WUs, is OpenCL 1.2 faster at crunching than 1.1??? What will the latest Drivers do in combination with Lunatics 0.43b on my two systems???


TL


I did a lot of testing on a friends 750Ti.
This card is hard to opimize for AP.
Check the read me file. Tips section for comand line options.
With each crime and every kindness we birth our future.
ID: 1704362 · Report as offensive
atlov

Send message
Joined: 11 Aug 12
Posts: 35
Credit: 19,309,460
RAC: 23,318
Germany
Message 1704380 - Posted: 23 Jul 2015, 21:18:31 UTC - in response to Message 1704349.  

Kudos to Richard and all those who contributed!


I've just downloaded Drivers from 347.88 to 353.30 for Win XP Pro x64 for Exeter, and the same for Win 7 Pro x64 for Prometheus.

For AP WUs, is OpenCL 1.2 faster at crunching than 1.1??? What will the latest Drivers do in combination with Lunatics 0.43b on my two systems???


I had a few APs left from the recent rush, so I can supply some numbers from my GTX660. I'm not using customized command line parameters and <count> is 1. No screen lags were experienced.
rev2737 (0.43a release), 347.88 driver: runtime 38:06
rev2887 (0.43b release), 347.88 driver: runtime 39:33
rev2887 (0.43b release), 353.30 driver: runtime 41:09
GPU load is more or less the same, ~97%.
ID: 1704380 · Report as offensive
Profile TimeLord04
Volunteer tester
Avatar

Send message
Joined: 9 Mar 06
Posts: 18641
Credit: 9,776,343
RAC: 260
United States
Message 1704436 - Posted: 23 Jul 2015, 23:19:44 UTC - in response to Message 1704380.  

Kudos to Richard and all those who contributed!


I've just downloaded Drivers from 347.88 to 353.30 for Win XP Pro x64 for Exeter, and the same for Win 7 Pro x64 for Prometheus.

For AP WUs, is OpenCL 1.2 faster at crunching than 1.1??? What will the latest Drivers do in combination with Lunatics 0.43b on my two systems???


I had a few APs left from the recent rush, so I can supply some numbers from my GTX660. I'm not using customized command line parameters and <count> is 1. No screen lags were experienced.
rev2737 (0.43a release), 347.88 driver: runtime 38:06
rev2887 (0.43b release), 347.88 driver: runtime 39:33
rev2887 (0.43b release), 353.30 driver: runtime 41:09
GPU load is more or less the same, ~97%.

I'm NOT using customized command line parameters, either, because I'm NOT familiar with how to make them work, or where to place them. I just install Lunatics, and let it crunch. I have told Lunatics to use CUDA50 for MB, and to allow APs to crunch on the NVIDIA cards.

Currently have Lunatics 0.43b running on both systems. NVIDIA Driver 337.88, also, on both systems.

I just thought that, now, with Lunatics 0.43b able to utilize the latest NVIDIA Drivers with OpenCL 1.2 that it might be worth upgrading the NVIDIA Drivers. Just needed to know which Driver to make use of. I was hoping that utilizing OpenCL 1.2 would be better than OpenCL 1.1 - I don't understand the difference between the two.

I notice that the run times you have posted actually show that OpenCL 1.2 on 353.30 is a couple minutes longer running than 347.88. I would have thought that run times would have gone down... :-/

The most complex game I run is StarCraft and BroodWar. (I don't even have StarCraft II.) So, I don't need the latest Drivers for anything but BOINC and SETI, Beta, and Einstein work.

I will upgrade to 353.30 on both systems; now that I'm able to, and see what happens.


TL
TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
ID: 1704436 · Report as offensive
Profile TimeLord04
Volunteer tester
Avatar

Send message
Joined: 9 Mar 06
Posts: 18641
Credit: 9,776,343
RAC: 260
United States
Message 1704484 - Posted: 24 Jul 2015, 2:12:06 UTC

Well, I've been fighting with Prometheus for three hours on Prometheus to Upgrade Drivers from 337.88. Unfortunately, complicating matters is that the Gigabyte Motherboard on Prometheus has an installed GeForce 9400 card that CANNOT be turned off. This caused the latest Drivers, (353.30, 353.06, 352.86, and 347.88), to fail to install - EVEN when running Display Driver Uninstaller in Safe Mode to remove prior drivers. Upon install of 353.30, after the reboot, the 750 TI SC was ONLY seen by GPU-Z as "Standard VGA Adapter". No matter how many times I ran DDU and tried the next highest Driver, the same thing happened. I just FINALLY got 337.88 reinstalled, and NOW the 750 TI SC is seen normally again by GPU-Z and BOINC!!! So, I'm stuck on Prometheus with 337.88 as my latest Driver.

Exeter; however, successfully installed 353.30 for the GTX-760. So, at least one system is completely updated. :-/


TL
TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
ID: 1704484 · Report as offensive
Profile TimeLord04
Volunteer tester
Avatar

Send message
Joined: 9 Mar 06
Posts: 18641
Credit: 9,776,343
RAC: 260
United States
Message 1704530 - Posted: 24 Jul 2015, 4:42:51 UTC

Thanks Richard for the work on Lunatics 0.43b. It's running fine on both systems; but, Exeter is making the best use of it combined with Driver 353.30. I can't wait for Exeter to get APs again to make use of OpenCL 1.2. :-)

It's unfortunate, due to hardware limitations on Prometheus, that I can't get the same performance. :-(

Thanks for the information on the Drivers' times to run information, Atlov. I will keep an eye on Exeter, (GTX-760), to see how it handles 353.30 and Lunatics 0.43b.

With that, goodnight everyone. :-)


TL
TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
ID: 1704530 · Report as offensive
Profile zoom314
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 59793
Credit: 43,563,790
RAC: 5,363
United States
Message 1704535 - Posted: 24 Jul 2015, 5:19:20 UTC

Panda Free a/v treats v0.43b as a threat and locks it, then like any virus moves the installer to it's chest, I had to restore the file to the hdd from within Panda, then exclude v0.43b to tell Panda, hands off, then I installed v0.43b like normal.
H.R. 1469 Cuts SSI, EITC, ACA, Medicaid, SNAP, LiHeap, Heap, etc, etc, etc, all temporary, w/a 5yr lifetime limit like TANF! Can't work? Die!!
ID: 1704535 · Report as offensive
qbit
Volunteer tester
Avatar

Send message
Joined: 19 Sep 04
Posts: 630
Credit: 6,868,528
RAC: 0
Austria
Message 1704579 - Posted: 24 Jul 2015, 10:21:43 UTC - in response to Message 1704530.  
Last modified: 24 Jul 2015, 10:27:27 UTC

Thanks Richard for the work on Lunatics 0.43b. It's running fine on both systems; but, Exeter is making the best use of it combined with Driver 353.30. I can't wait for Exeter to get APs again to make use of OpenCL 1.2. :-)

It's unfortunate, due to hardware limitations on Prometheus, that I can't get the same performance. :-(

Thanks for the information on the Drivers' times to run information, Atlov. I will keep an eye on Exeter, (GTX-760), to see how it handles 353.30 and Lunatics 0.43b.

With that, goodnight everyone. :-)


TL

I'm afraid you won't see any change in performance just because of the driver. At least I didn't notice any afaicr.
ID: 1704579 · Report as offensive
Profile Blurf
Volunteer tester

Send message
Joined: 2 Sep 06
Posts: 8864
Credit: 11,354,558
RAC: 5,345
United States
Message 1704640 - Posted: 24 Jul 2015, 14:44:26 UTC

What are the changes I need to make again to have my machine crunch 2 Seti GPU units simultaneously again please? I can't find the changes that I was helped with previously.

Thx


ID: 1704640 · Report as offensive
Profile Blurf
Volunteer tester

Send message
Joined: 2 Sep 06
Posts: 8864
Credit: 11,354,558
RAC: 5,345
United States
Message 1704647 - Posted: 24 Jul 2015, 15:10:24 UTC

Thx to Zalster for helping me.


ID: 1704647 · Report as offensive
Profile Keith MyersProject Donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 2421
Credit: 183,376,445
RAC: 349,883
United States
Message 1704651 - Posted: 24 Jul 2015, 15:23:15 UTC - in response to Message 1704640.  

Either go the long way and edit <count>1</count> from to <count>0.5</count> througout the app_info file. Or much easier create an app_config in each project directory with Notepad and set the GPU utilization there with statements like this:


<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.10</cpu_usage>
</gpu_versions>
</app>

<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
</app_config>


That way you don't have to ever edit app_info again and possibly lose all your work. Much easier to edit or change app_config to make later changes and it will never lose your work. I suggest the latter.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1704651 · Report as offensive
1 · 2 · Next

Message boards : Number crunching : Lunatics Windows Installer v0.43b Maintenance Release


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.