Welcome to MilkyWay@home

Posts by nanoprobe

21) Message boards : News : Separation updated to 1.00 (Message 53098)
Posted 12 Feb 2012 by nanoprobe
Post:
5850 is double precision.
22) Message boards : News : Separation updated to 1.00 (Message 53095)
Posted 11 Feb 2012 by nanoprobe
Post:
Thanks
23) Message boards : News : Separation updated to 1.00 (Message 53091)
Posted 11 Feb 2012 by nanoprobe
Post:
For completeness, I might maybe should have added that I'm using the stock 1.02 from the project, no app_info file.

the app_info.xml file really isn't necessary unless you either want to change the number of simultaneously running MW@H tasks to something greater than 1 or improve GUI lag/set process priority/etc. via command line parameters.

What command would be added to the the app-info file to throttle back GPU usage? It's currently at 99% and I'd like to pull it back to 80-85%.
Win7 64 bit. Radeon 5830.
24) Message boards : News : Separation updated to 1.00 (Message 53065)
Posted 10 Feb 2012 by nanoprobe
Post:

This is exactly what to expect if you are using 7.x.x with 'old style' cache settings - something like CE=0 and ED=3.0 for example.

The new cache settings in BOINC 7.0.xx are a real PITA but if you set connect everyday to 1.00 and additional cache to 0.50 you should get work.
XP 32 and WIN7 64 both crunching away. It's the connect everyday setting that is the most important with the newer versions.
25) Message boards : News : Separation updated to 1.00 (Message 52992)
Posted 10 Feb 2012 by nanoprobe
Post:
Thought 11.9 should be working for XP 32bit with HD5850?

12.1 is working for me on XP 32 bit with a 5830 but I'm using the 0.82 separation app not the 1.00.
26) Message boards : News : Separation updated to 1.00 (Message 52986)
Posted 9 Feb 2012 by nanoprobe
Post:
Still can't get any WUs for my XP 32 bit box if I use the app_info I was using before to reduce the GPU usage. Worked fine before. Anyone have a suggestion. File used is below.
<app_info>

<app><!-- GPU app v0.82 for MW Separation -->
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_0.82_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>82</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1.0</count>
</coproc>
<cmdline>--gpu-target-frequency 80 --gpu-polling-mode 16 --process-priority 1</cmdline>
<file_ref>
<file_name>milkyway_separation_0.82_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>

</app_info>

Never mind. I figured it out for XP 32 bit. Can someone help me with an app_info command that will throttle down the GPU on Win7 64 bit?
Thanks in advance.
27) Message boards : News : Separation updated to 1.00 (Message 52979)
Posted 9 Feb 2012 by nanoprobe
Post:
Still can't get any WUs for my XP 32 bit box if I use the app_info I was using before to reduce the GPU usage. Worked fine before. Anyone have a suggestion. File used is below.
<app_info>

<app><!-- GPU app v0.82 for MW Separation -->
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_0.82_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>82</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1.0</count>
</coproc>
<cmdline>--gpu-target-frequency 80 --gpu-polling-mode 16 --process-priority 1</cmdline>
<file_ref>
<file_name>milkyway_separation_0.82_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>

</app_info>
28) Message boards : News : Separation updated to 1.00 (Message 52897)
Posted 9 Feb 2012 by nanoprobe
Post:
Is there a command that can be added to the app-info file that will throttle back the GPU usage. It's now running @ 99% and I really don't want to run it that hard.
Thanks.
29) Message boards : News : Separation updated to 1.00 (Message 52881)
Posted 8 Feb 2012 by nanoprobe
Post:
Using 7.0.14 with the above posted ap-info file, detached and reattached and still getting no work.

EDIT: Working. In my haste I misnamed the app_info file. *slaps forehead*
30) Message boards : Cafe MilkyWay : Milestones III (Message 52843)
Posted 7 Feb 2012 by nanoprobe
Post:

Took the side off the case so..


Here is a little trick I use to keep the dust out if you've removed the side cover. Find the largest window AC filter you can buy.( They look like a thin piece of sponge) Also buy a roll of velcro tape. Take the prickly side of the tape and place it around the edges of the tower. Stick the filter to it and trim off the excess. Done. Remove filter when necessary, clean and replace. I have 2 towers running with this and it works great.
31) Message boards : Number crunching : XP 32 question (Message 52809)
Posted 4 Feb 2012 by nanoprobe
Post:
Cant help with the detail of the settings as I dont use the cmd line arguements, but whilst waiting for someone who does .... its going to help them if you describe a little more what you mean by bogging down.

eg mouse gittery, screen slow to redraw, scrolling inside individual windows juddery, juddery when moving a window, screen blemishes, active BOINC window not refreshing the counters.... others ...

all the above rofl :)

Regards
Zy

My definition of bogging down is everything is slow to react to mouse, left or right click, scrolling. opening any programs, launching browser and of course the BOINC window lagging way behind on the counters. Pretty much everything you described.
32) Message boards : Number crunching : XP 32 question (Message 52803)
Posted 4 Feb 2012 by nanoprobe
Post:
My gpu-polling-mode and process-priority are set the same as yours but I can't run 2 WUs simultaneously without bogging the system down. What settings would you suggest I try to help with this issue? Here is my current app-info xml file.

<app_info>

<app><!-- GPU app v0.82 for MW Separation -->
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_0.82_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>82</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1.0</count>
</coproc>
<cmdline>--gpu-target-frequency 75 --gpu-polling-mode 16 --process-priority 1</cmdline>
<file_ref>
<file_name>milkyway_separation_0.82_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>

</app_info>
33) Message boards : Number crunching : XP 32 question (Message 52798)
Posted 3 Feb 2012 by nanoprobe
Post:
Thanks for the file. It worked for 1 task but the GPU still runs at 98% with 2 tasks running at the same time. I tried it with settings from 60-85 in the file but it still ran 2 @ 98%. With you file settings the GPU runs @ 81% and each WU takes 2 minutes. I can live with that. Thanks again.
34) Message boards : Number crunching : XP 32 question (Message 52789)
Posted 3 Feb 2012 by nanoprobe
Post:
FWIW the GPU was at 97% on the Win7 box.
35) Message boards : Number crunching : XP 32 question (Message 52787)
Posted 3 Feb 2012 by nanoprobe
Post:
If you use GPU-Z I bet it shows your GPU being used at 98+%. No wonder your switch between programmes and other applications is slow. You need an app_info.xml file to bring the GPU usage down to 90% to 95%.

That is what I did on my XP 32 bit box.

It was at 99% according to GPU temp. Can you post your app-info.xml file for me?
Thanks.
36) Message boards : Number crunching : XP 32 question (Message 52785)
Posted 3 Feb 2012 by nanoprobe
Post:
Could you be a bit more specific about "bogs down?" Just graphics lag? It shouldn't be different. I don't see any real difference between the timings of the GPU results from either of your system which is what I would assume your problem is

What I mean by bogs down is that opening and closing any programs, web pages, anything, takes minutes. Even trying to navigate the BOINC manager is VERY slow. It's not the run time. Like you said, they're about the same.
If I can't solve this issue than I will have to discontinue running M@H on this computer.
37) Message boards : Number crunching : XP 32 question (Message 52782)
Posted 3 Feb 2012 by nanoprobe
Post:
I have M@H running on one machine with Win7 64 and a 5830 card with no problems. I have the same card running on an XP pro SP3 32 bit box that has issues. Whenever M@H is running it bogs down the computer so much as to make it unusable. I've tried a few different things to no avail.
i7-860
4 GB ram
Brand new Seasonic 620w PSU
POEM runs on this computer without problems. Is it because M@H requires a 64 bit OS?
38) Message boards : Cafe MilkyWay : Milkyway chit chat - drop in and say hello! (Message 52773)
Posted 2 Feb 2012 by nanoprobe
Post:
Slowly (very slowly) learning the ropes of GPU crunching. Starting to get it all sorted out little by little. Next challenge is to get some Nvidia cards to run other Nvidia only projects. Glad to be here.


Previous 20

©2024 Astroinformatics Group