I have seen that works from application "MilkyWay@Home N-Body Simulation v0.66 (mt)" take YEARS to complete. Okey, not years, but a very log time. Works from "MilkyWay@Home v0.88" takes only 8 - 10 hours to compete for me. How can I block works from "MilkyWay@Home N-Body Simulation v0.66 (mt)"? In the SETI or Einstein project I can block applications to send me works. Can I do that here too?

Here at mw there is no way to select which type of CPU work your pc gets - at least not in your account configuration.

But you can use an app_info.xml file to restrict your pc to wm@home apps only. The following message contains a download link to a SSE optimized exe, an appropriate app_info.xml and a textfile with instruction on how to install the exe and xml files.

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2473&nowrap=true#50045

Well, thanks. Should the file be coded as ASCII? And in what format? UFT-8?

And where should I have the .xml document? In the projects root folder?

Sorry, i didn't notice that there is no instruction.txt file contained in the download.

First download the MilyWay@Home Windows 32/64 bit SSE3 INTEL CPUs ONLY Science App from http://www.mpits.net/opt_mw.php.
This should be the correct one for your type of computer/OS.

Installation of the optimized app is simple.

1) Stop BOINC service by going to the advanced menu and selecting "Shut down connected client, click okay and then click cancel. Then exit out of the BOINC Manager.

2) The zip file you've downloaded contains 2 files, an exe and an app_info.xml file. Extract both files into your BOINC\projects\milkyway.cs.rpi.edu_milkyway folder.

Windows 98/SE/ME: C:\Windows\All Users\BOINC\ or C:\Windows\Profiles\All Users\BOINC\

Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC\

Windows Vista and Windows 7: C:\ProgramData\BOINC\

3) Restart BOINC service by reopening BOINC Manager.

That's it, you're done! You can open your task manager to see that it's really the new optimized app crunching your WUs.

BOINC will tell you that it found app_info.xml and is using an "anonymous platform".


Happy crunching!

Sorry, i didn't notice that there is no instruction.txt file contained in the download.

First download the MilyWay@Home Windows 32/64 bit SSE3 INTEL CPUs ONLY Science App from http://www.mpits.net/opt_mw.php.
This should be the correct one for your type of computer/OS.

Installation of the optimized app is simple.

1) Stop BOINC service by going to the advanced menu and selecting "Shut down connected client, click okay and then click cancel. Then exit out of the BOINC Manager.

2) The zip file you've downloaded contains 2 files, an exe and an app_info.xml file. Extract both files into your BOINC\projects\milkyway.cs.rpi.edu_milkyway folder.

Windows 98/SE/ME: C:\Windows\All Users\BOINC\ or C:\Windows\Profiles\All Users\BOINC\

Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC\

Windows Vista and Windows 7: C:\ProgramData\BOINC\

3) Restart BOINC service by reopening BOINC Manager.

That's it, you're done! You can open your task manager to see that it's really the new optimized app crunching your WUs.

BOINC will tell you that it found app_info.xml and is using an "anonymous platform".


Happy crunching!

So it will ONLY got tasks from MW@Home, and not MW@Home N-Body Simulation (mt)?

So it will ONLY got tasks from MW@Home, and not MW@Home N-Body Simulation (mt)?

Exactly - and the MW@Home tasks will finish much faster because the optimized app will use the SSE3 instruction set of your INTEL PC.

How does it works?

<app_info>
  <app>
    <name>milkyway</name>
  </app>
  <file_info>
    <name>milkyway_separation_0.91_windows_intelx86_sse3.exe</name>
    <executable />
  </file_info>
  <app_version>
    <app_name>milkyway</app_name>
    <version_num>91</version_num>
    <flops>1.0e11</flops>
    <avg_ncpus>1</avg_ncpus>
    <max_ncpus>1</max_ncpus>
       <file_ref>
      <file_name>milkyway_separation_0.91_windows_intelx86_sse3.exe</file_name>
      <main_program/>
    </file_ref>
  </app_version>
</app_info>

The ps_separation_13_3s_fix20_2_1335310_0 tasks are also impossible to complete by the deadline as well. 250 hrs +/- is quite a long time for computing. The deadline is in 2 weeks, but I crunch only 12hrs a day at max during the week, and BOINC MGR is running this task at high priority since I run 3 other projects as well.

Is there a way to restrict this kind of task from my system or is this the newest style of task to come out? Can I change some parameter to say maybe take all 4 cores and crunch it quick and send it back? I notice that the task is not using all 4 cores like the NOBODY tasks, which I suppose is good and bad.

Maybe you guys can extend the deadline on these huge tasks to 3 weeks so BOINC runs normally instead of high priority? Or maybe you can set the code so it uses all 4 cores but cycles like the other BOINC tasks?

Just some thoughts.

The ps_separation_13_3s_fix20_2_1335310_0 tasks are also impossible to complete by the deadline as well. 250 hrs +/- is quite a long time for computing. The deadline is in 2 weeks, but I crunch only 12hrs a day at max during the week, and BOINC MGR is running this task at high priority since I run 3 other projects as well.

Is there a way to restrict this kind of task from my system or is this the newest style of task to come out? Can I change some parameter to say maybe take all 4 cores and crunch it quick and send it back? I notice that the task is not using all 4 cores like the NOBODY tasks, which I suppose is good and bad.

Maybe you guys can extend the deadline on these huge tasks to 3 weeks so BOINC runs normally instead of high priority? Or maybe you can set the code so it uses all 4 cores but cycles like the other BOINC tasks?

Just some thoughts.

I would also run the huge works, but the deadline is too short.

The ps_separation_13_3s_fix20_2_1335310_0 tasks are also impossible to complete by the deadline as well. 250 hrs +/- is quite a long time for computing.

Is that just the estimated time to complete? And if yes, is it possible that your DCF is waaay off?

IIRC my Pentium M @1.73GHz Laptop needs about 18 hours CPU time on these tasks, your Core 2 Quad @2.5GHz should be quite a bit faster (per core), so if the DCF is not close to 1 you can set it to 1.something in client_state.xml.

---

What is weird is that 5hrs later the task was complete.
Something is goofy for sure.
I think BOINC has a hard time computing the finish time on these tasks.
The last giant task I had did take forever and a life time to finish hogging all 4 cores for nearly a week. Think that was one of the NBODY tasks on the .82 software.

Now DCF, I don't know that term.
Maybe you could tell me what you mean?

Well, I don't get any credits.

What is weird is that 5hrs later the task was complete.
Something is goofy for sure.

Well that's clear singn of the local DCF being wrong.

Now DCF, I don't know that term.
Maybe you could tell me what you mean?

Duration correction factor is one of the values used by BOINC to calculate the run time of tasks. After you have completed 10 tasks the server side DCF kicks in for each app separately, and the local DCF have to adjust to that. It's done that way because each app is different fast and there's only one local DCF for the project, so the server tries to adjust the estimates for each task so the local DCF is always around 1.

You can find it in client_state.xml (BOINC data directory), there's one for each project:

<project>
    <master_url>http://milkyway.cs.rpi.edu/milkyway/</master_url>
[i](...)[/i]
    <duration_correction_factor>1.195674</duration_correction_factor>

You have to close BOINC before you edit this file and eventually create a complete backup of the folder. However, if you don't feel comfortable with editing this file, you can just wait till BOINC self gets the DCF right, but it might take some time.

---

Ok thanks for the info.
I think you are on to something.
Last night before I went to bed a 4 core task was running.
It said 16hrs to completion, and I just checked and it completed in 4hrs.
I'll have a look later on and try and make that correction.
Thanks

What is weird is that 5hrs later the task was complete.
Something is goofy for sure.
I think BOINC has a hard time computing the finish time on these tasks.
The last giant task I had did take forever and a life time to finish hogging all 4 cores for nearly a week. Think that was one of the NBODY tasks on the .82 software.

Now DCF, I don't know that term.
Maybe you could tell me what you mean?

Same here I get 147 hour jobs from seti all the time. I use to turn them back but one day I was bored and just watched the time drop off in 20 minute segments per second or every two seconds it was wild to watch.

Dave

Now if there was only an optimized app based on linux that I could use for MW that would be great. lol oh and it has to be as easy to install as the windows one hehehe

aw bo I found some but the pages are all 404ed sniff. LOL

we need to donate one of these to some one man would all the projets get done fast:)

http://www.youtube.com/watch?v=l8FUmS1h-5U&feature=related

See here and my following post. If you want your CPU to do worthwhile work it would actually be the N-Body tasks.

MrS

---

Scanning for our furry friends since Jan 2002

we need to donate one of these to some one man would all the projets get done fast:)
http://www.youtube.com/watch?v=l8FUmS1h-5U&feature=related

It would be slower here than a normal PC with 2 HD 6970 AMDs.

but it has 960 cores. lol those Teslas are what I am going to put in my first computer I build. Next year I hope.

ok back to the story I can't find a folder just for MW where would it be located on a linux system? and I am so just thinking of running boinc in wine so I can just simplify my life and get the optimised aps to run there what you think?

guess I need some one to come to skype or yahoo and walk me thru the first tar.gz thing because I know all I get when I try is errors so I must be doing something wrong. LOL