Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
1)
Message boards :
Number crunching :
Short Title List
(Message 75619)
Posted 3446 days ago by Zydor
woa .... that was fast ..... many thanks :)
Edit:
Thinking about it ..... would be good to put the short title next to the long title name in the configuration list, eg:
PPS Sieve [Short Title: pps_sr2sieve]
.....
Proth Prime Search (LLR) [Short Title: llrPSP]
etc ...
|
2)
Message boards :
Number crunching :
Short Title List
(Message 75617)
Posted 3446 days ago by Zydor
Currently turning the 'ol rusty cogs not having crunched here for a while.
It would be of great assistance if the WU Project short titles for the app_config.xml (eg Short Title: pps_sr2sieve), were included alongside the descriptions in the preferences list where we tick the box for preferred apps.
Here's where I discover a separate list of short titles exists elsewhere no doubt :)
..... such would be the way of life :)
|
3)
Message boards :
Number crunching :
AMD and NVidia GPU Hardware Mix in same PC
(Message 74768)
Posted 3475 days ago by Zydor
If you need, by other reason, to use app_info, ....
oooops .... meant to say app_config not app_info ....showing me age rofl :)
Suspect : Then, on the preferences page, select use ATI and NVIDIA GPU.
.... is where its going wrong, I'll pass it on to select both in preferences with a caviat, and see how she goes .... many thanks :)
|
4)
Message boards :
Number crunching :
AMD and NVidia GPU Hardware Mix in same PC
(Message 74764)
Posted 3475 days ago by Zydor
This has come up before in these Forums - but danged if I can find it ..... :)
Anyone have the format for app_info.xml to run 1xAMD card and 1xNVidia card on the same machine, concurrently, for the same Project (running the appropriate apps AMD or NVidia for the Project)
The 'ol fella with the sledgehammer is tapping on the inside of my skull that there is a way of doing this ..... but its possible he's getting senile in his old age rofl :)
(To be Up Front, this is for another Project, but its equally applicable here for those with a mix of AMD and NVidia cards on the same machine who want to run such a mix simultaneously on Prime Grid Apps)
You can assume an app does exist for each of the different GPU types for the Project concerned. The issue is accessing both types at the same time, on the same machine.
Any ideas anyone ?
|
5)
Message boards :
Proth Prime Search :
Intel HD GPU app?
(Message 67394)
Posted 3741 days ago by Zydor
The last time such "faking" of the server was proposed, Raistmer quickly said not to use it.
http://setiathome.berkeley.edu/forum_thread.php?id=70717&postid=1371243
Whether that's correct or not in this case, what you are raising propels it into the 0.1% of cases where app_info has to be used.
Where care needs taking is to create an impression that app_config connot be used at all on a Project. It is now by far the preferred and recomended method, and app_info is now the fallback for special cases.
To leave it open where the impression is given that this project has to use app_info or nothing is not a route we should be going down
|
6)
Message boards :
Proth Prime Search :
Intel HD GPU app?
(Message 67392)
Posted 3741 days ago by Zydor
And even if the server did know it, there is no app available for opencl_intel_100 plan class.
In that case there is no point is telling it something it cant use as its not available....
When it becomes available the server will already be aware and doesn't need telling.
That's why app_config works and saves huge time - all we are doing is telling the server what it doesn't know ... in ten lines.
|
7)
Message boards :
Proth Prime Search :
Intel HD GPU app?
(Message 67389)
Posted 3741 days ago by Zydor
Below is the app_info in question, I have highlighted what the server (now) doesn't know. The bolded information is all the Server now needs, a full blown app_info is not required. If individuals wish to use an app_info, that's fine, but its telling the server what it already knows, and becomes pointless.
The only time an app_info is now needed is when:
1. A different app version other than the general release is run(eg testing a new app)
2. You wish to run non standard configurations and settings (overwhelming vast majority of time, the server knows better than you do what the optimum fine detail settings are)
The bold parts below are the only things the server doesn't know, and needs telling in an app_config
<app_info>
<app>
<name>pps_sr2sieve</name>
</app>
<file_info>
<name>primegrid_tpsieve_1.39_windows_intelx86__atiPPSsieve.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>pps_sr2sieve</app_name>
<version_num>139</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>1.00</avg_ncpus>
<max_ncpus>1.00</max_ncpus>
<plan_class>opencl_intel_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>intel_gpu</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>primegrid_tpsieve_1.39_windows_intelx86__atiPPSsieve.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>pps_sr2sieve</app_name>
<version_num>139</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>primegrid_tpsieve_1.39_windows_intelx86__atiPPSsieve.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
Everything else - not in bold letters- is superfluous, it already knows, hence the reason only an app_config is needed. Essentially all the user now does is say "I want to run "x" CPU apps and "Y" GPU apps, please send me the new apps automatically when published". An app_config.xml version of your app_info is:
<app_config>
<app>
<name>pps_sr2sieve</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app>
</app_config>
After that, that's it, the server will update the application automatically, and you don't need to write a new app_info. Those ten lines above replace your app_info. If you wish to write an app_info, go ahead, no problem, but its wholey superfluous now and not required. As noted above the app_config stays for ever and a day, it will send new apps automatically when versions change.
app_config.xml is small and "fire and forget". However, if for some reason you wish to use app_info, use it - just be aware all you are doing is telling the server what it already knows, and that's pretty pointless at the end of the day.
|
8)
Message boards :
Proth Prime Search :
Intel HD GPU app?
(Message 67387)
Posted 3741 days ago by Zydor
Yes it does replace it .... you cannot run both at the same time
If there are more complex things to do then an app_info must be used.
However, 99.9% of tasks can now be completed using an app_config, and app_info is no longer needed, as the server will now automatically detect 99% of what it needs by querying the PC without your intervention (which is why its so small), without what used to be supplied by the User in an app_info.
The two complement each other - but - they are mutually exclusive, they must not, and cannot, be run at the same time.
|
9)
Message boards :
Proth Prime Search :
Intel HD GPU app?
(Message 67375)
Posted 3741 days ago by Zydor
Thanks Zydor. I know about that.
But I don't know how to configure it to run PPSieve on Intel GPU.
For this to work, you must be running BOINC 7.0.40+
Try this, paste it into the project directory (create it with Notepad) and call it "app_config.xml" (no quotes) :
<app_config>
<app>
<name>pps_sr2sieve</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app>
</app_config>
(do NOT use an app_info when using app_config, app_info is replaced by the app_config)
That example will run two instances of the app, one each on two GPU cores. If you only want to run one instance, change:
<max_concurrent>2</max_concurrent> to: <max_concurrent>1</max_concurrent>
The <cpu_usage> section above will give 0.1 cpu core per GPU app instance. If you wanted more cpu allocated per gpu instance you change it ... for example:
<cpu_usage>0.2</cpu_usage> gives you 0.2 cpu core per gpu instance
The <max_concurrent> section is there to show the TOTAL number of instances run, ie the ADDITION of both GPU and CPU instances on the machine. However in your case you are only running GPU apps not CPU as well, so you dont have that additional complication. Just note it for future use.
If you are running two or more GPUs, make sure you have a suitably amended cc_config in the BOINC directory, for example:
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
Without that its likely BOINC will only recognise one GPU, whatever you put inside the app_config.
Once all that is set, thats it - all future updates are done server-side by the Project Team, you'll never need to change it unless your hardware (CPU/GPU) changes, the Project Team will automatically supply updated exe file as they are created, you just crunch on :)
Full format instructions are at (scroll to the bottom of the page):
http://boinc.berkeley.edu/wiki/Client_configuration
|
10)
Message boards :
Proth Prime Search :
Intel HD GPU app?
(Message 67374)
Posted 3741 days ago by Zydor
Thanks Zydor. I know about that.
But I don't know how to configure it to run PPSieve on Intel GPU.
Prime Grid apps are app_config enabled at the server, what I cant remember is the short title for the app_config to run PPSieve (it actually maybe PPSieve - but I am checking trying to find what the short title is for the app_config.
Meanwhile .... have a look at:
http://boinc.berkeley.edu/dev/forum_thread.php?id=8051&postid=47760
Messages: 47760, 47762 and 47763. You only need use an app_info when running an app version that's not current at the Project - the other 99% of times, app_config will do the job far better, with less messing around - all the work is done server-side.
|
Next 10 posts
|
