Welcome to MilkyWay@home

Posts by Jim Wilkins

1) Message boards : Number crunching : N-Body long processing time (Message 62622)
Posted 24 Oct 2014 by Jim Wilkins
Post:
I gave up. I was going to shoot way past the deadline. I've turned off the N-body WUs for now.
2) Message boards : Number crunching : N-Body long processing time (Message 62579)
Posted 16 Oct 2014 by Jim Wilkins
Post:
I have one running 17% for 36 hours. It's deadline is Oct. 26, so I'm just going to let it run. Since it does not affect my other work, I'm curious about what will happen.
3) Message boards : Number crunching : Badges locate (Message 60843)
Posted 28 Jan 2014 by Jim Wilkins
Post:
Thx.
4) Message boards : Number crunching : Badges locate (Message 60837)
Posted 28 Jan 2014 by Jim Wilkins
Post:
Where do I find my badges in my account?

Thanks,
Jim
5) Message boards : Number crunching : N-Body Search Simulation using all CPUs (Message 59554)
Posted 8 Aug 2013 by Jim Wilkins
Post:
Thanks,

Jim
6) Message boards : Number crunching : N-Body Search Simulation using all CPUs (Message 59551)
Posted 8 Aug 2013 by Jim Wilkins
Post:
Thanks for the response. However, that control applies to all apps that are running. For instance, what I want to do is run MW on one CPU and run other apps on the remaining three CPUs. BTW, this is a Mac system, but your response still applied.

Jim
7) Message boards : Number crunching : N-Body Search Simulation using all CPUs (Message 59549)
Posted 8 Aug 2013 by Jim Wilkins
Post:
Hi all,

The N-Body app is using all of my CPUs (4). I really only want it to use 1-2. Can I control this?


Update: It just aborted with a computation error.
8) Message boards : Number crunching : N-Body Search Simulation using all CPUs (Message 59548)
Posted 8 Aug 2013 by Jim Wilkins
Post:
Hi all,

The N-Body app is using all of my CPUs (4). I really only want it to use 1-2. Can I control this?
9) Message boards : Number crunching : SLow running WU (Message 38869)
Posted 19 Apr 2010 by Jim Wilkins
Post:
This one finish in about 18 hours CPU time. Go figure.
10) Message boards : News : bad workunits (Message 38868)
Posted 19 Apr 2010 by Jim Wilkins
Post:
FWIW, the last two WUs that I have rub on MWH .26 and OSX 10.6.3 both were somewhat strange. One took 8 hours to get to 2-3% and then finished in another 10 hours. The other experienced the "no checkpoint" problem. It had run for 8-9 hours, then I shut BOINC (and my computer) down for the night. This morning, it restarted from scratch.

Jim
11) Message boards : Number crunching : SLow running WU (Message 38845)
Posted 18 Apr 2010 by Jim Wilkins
Post:
Well, now it has been running for 13 hrs and it is 60% complete. I must have been stuck in some long initialization sequence. Last checkpoint happened about 45 minutes ago.

Jim
12) Message boards : Number crunching : SLow running WU (Message 38831)
Posted 18 Apr 2010 by Jim Wilkins
Post:
I'm not sure if this is a problem or not but I have a WU running for over 8 hours CPU time and it is only at 2.5% complete. It does seem to be pick up speed now. Using Intel Mac, MW vers 0.26.

Jim
13) Message boards : Number crunching : Giant Workunits? (Message 9623)
Posted 3 Feb 2009 by Jim Wilkins
Post:
Actually, I am seeing the opposite. Tiny estimated times (14 seconds) that take the normal 20-25 minutes.

Jim
14) Message boards : Number crunching : Is anyone glad with the project? (Message 9334)
Posted 29 Jan 2009 by Jim Wilkins
Post:
Well said.
15) Message boards : Number crunching : v0.17 for windows (Message 9317)
Posted 28 Jan 2009 by Jim Wilkins
Post:
My third XP result has the same result.

Jim
16) Message boards : Number crunching : v0.17 for windows (Message 9316)
Posted 28 Jan 2009 by Jim Wilkins
Post:
The state was valid on both of the .17 WUs, so I guess they generated data.
17) Message boards : Number crunching : v0.17 for windows (Message 9314)
Posted 28 Jan 2009 by Jim Wilkins
Post:
I have many .16 WUs for my Intel Mac and I don't see this in them. I have just 2 results for my XP machine and I see this in both of them.

Jim
18) Message boards : Number crunching : v0.17 for windows (Message 9312)
Posted 28 Jan 2009 by Jim Wilkins
Post:
FWIW, I am seeing this result on .17 WUs:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233321225.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233321225.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct

</stderr_txt>
]]

Jim
19) Message boards : Number crunching : app v12 (Message 8751)
Posted 20 Jan 2009 by Jim Wilkins
Post:
Using 4 samples, I am seeing a consistent 5% improvement in performance on my 2,66Mhz, 2 dual core MacPro. That equate to about a minute plus for me.

Jim
20) Message boards : Number crunching : app v12 (Message 8717)
Posted 20 Jan 2009 by Jim Wilkins
Post:
On 1 sample, I have seen a 5% faster time with .12. Not sure if that is in the noise or not.

Jim

EDIT: Running Mac OS 10.5.6 using BOINC 6.2.18 on a 2 dual core MacPro.


Next 20

©2024 Astroinformatics Group