Welcome to MilkyWay@home

Posts by Jimbocous

1) Message boards : News : New Separation Runs 6/9/2021 (Message 71050)
Posted 3 Aug 2021 by Jimbocous
Post:
Thanks Jim and Al. That seems to make sense.

Upgrading may be an issue as I have the last version output by BOINC themselves.


I use an all-in-one BOINC version that just extracts to a directory. It was widely distributed at SETI. I can fix you up with a copy if you'd like ...
Alternately, if you want to try a PPA I can provide a link there as well.
2) Message boards : News : New Separation Runs 6/9/2021 (Message 71048)
Posted 3 Aug 2021 by Jimbocous
Post:
FWIW, both my Win10 and Ubuntu boxes mentioned above are running 7.16.x BOINC client.
3) Message boards : News : New Separation Runs 6/9/2021 (Message 71046)
Posted 3 Aug 2021 by Jimbocous
Post:
Just FYI.
Running same WUs here (CPU only) on 2 machines, 1 Win10 the other Ubuntu 18.0.4.
Not seeing any recent failures or errors on either.
My machines should be viewable if you want to compare.
Regards, Jim ...
4) Message boards : News : Separation Validator Updates/Brief Server Outage(s) (Message 70977)
Posted 18 Jul 2021 by Jimbocous
Post:
Much better here as well. Thanks for the fix!
5) Message boards : News : New Separation Runs 6/9/2021 (Message 70957)
Posted 11 Jul 2021 by Jimbocous
Post:
Seeing about a 20% invalid rate on my running hosts as well
(1 linux, 1 win10, both running CPU tasks only).
Good to see in the forum here the issue's being worked.
I'll take another look when I hear the change hits production.
Thanks!
6) Message boards : Number crunching : Setting some apps to GPU and some to CPU (Message 69676)
Posted 9 Apr 2020 by Jimbocous
Post:
In short THEY don't see a problem so there's no reason to fix anything, I'm not complaining just stating what I see.
Yeah, I looked at the list of apps (Thanks for that, Mikey) and Good Grief, the version and names and numbers are all the same regardless of platform or what ever.
To the degree that projects compete for the resources of volunteers it's right that one can easily move on to another, but that badly misses the point.
Whatever ...
7) Message boards : Number crunching : Setting some apps to GPU and some to CPU (Message 69652)
Posted 5 Apr 2020 by Jimbocous
Post:

You've got two different pc's just put them in different venues and on one run cpu wu's and on the other one run gpu wu's. Gpu and cpu wu's take vastly different times to run and your cache will never be right especially with the 10 minute timeout to get gpu wu's here at MilkyWay. Unfortunately MilkyWay is pretty happy with the way they do things so any changes, ie names of the apps or Server side timeout settings, aren't going to happen anytime soon.
Might want to rethink your suggestion there. As stated, I'm not sure what that would accomplish, except to leave CPUs idle on one machine and GPUs idle on the other.
As you noted, nothing new about the unwillingness in academia to see and adjust to reality. Don't get me started.:)
Some of this is really a BOINC issue, as well. It may have taken a PhD to write BOINC, but shouldn't require one to operate it.
I was hoping that somewhere on this site there was a listing of apps with app names and the like that I could use as a reference.
Bottom line: Giving two different apps the same name is just plain silly, even if they are manipulating the same data task.
8) Message boards : Number crunching : Setting some apps to GPU and some to CPU (Message 69648)
Posted 5 Apr 2020 by Jimbocous
Post:
Yeah, the above pretty much isn't going to happen, at least this way. While max_concurrent works within <app></app>, apparently if you try to nest it deeper, it's just ignored.
Now, if the GPU and CPU versions of "milkyway" had different app names, as I've seen at other projects, this is a piece of cake.
Seems like using the same app name for two different versions of an app is a pretty bad idea.
9) Message boards : Number crunching : Setting some apps to GPU and some to CPU (Message 69647)
Posted 5 Apr 2020 by Jimbocous
Post:
Sorry for the necro-thread, but I can't seem to find any other close references using site search or other docs that discuss project-specific app_config issues.
I'm trying to adjust my app_config.xml to control the max number of concurrent instances while trying to differentiate between CPU and GPU work.

I suspect the issue is that I need to define the plan_class for CPU as well as for GPU, and while I know from client_state.xml that my GPU work plan class is opencl_nvidia_101, I can't seem to locate a plan_class defined for CPU work, and without it the parameters seem to be ignored. (That assumes this is the right way to address the issue.)
What I'm trying to accomplish is something like this:
<app_config>
  <app>
    <name>milkyway</name>
    <gpu_versions>
      <gpu_usage>.5</gpu_usage>
      <cpu_usage>.05</cpu_usage>
    </gpu_versions>
  </app>

  <app_version>
    <app_name>milkyway</app_name>
    <plan_class> ???? </plan_class>            <!-- what is the p_c for CPU? -->
    <max_concurrent>1</max_concurrent>
  </app_version>

  <app_version>
    <app_name>milkyway</app_name>
    <plan_class>opencl_nvidia_101</plan_class>
    <max_concurrent>2</max_concurrent>
  </app_version>

</app_config>
Would appreciate it if anybody could get my mind right on this, or point me in the right direction!!
Thx, Jim ...
10) Message boards : Number crunching : Run Multiple WU's on Your GPU (Message 69585)
Posted 7 Mar 2020 by Jimbocous
Post:
Just curious to see if anyone has really studied whether there's an appreciable gain in running >1 WU/GPU?
New here at MW@H, but in previous tests at other projects I never saw any significant gain.
Regards, Jim ...




©2021 Astroinformatics Group