I just turned them off for a moment to transition some WUs. They will be back up shortly.

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 ...

Boinc does NOT benefit from using SLI, take it off if you are not a gamer, it's better to treat each gpu separately.

Hi all,

I noticed something interesting. Today I got new AIO water cooling for my old 2500K and overclock it default bios 3.2 to 4.2Ghz. When I look milkyway tasks percentace of "Completed, validation inconclusive" become high numbers then before. Mine R9 270x same not overclocked and same driver. Any thoughts about this ?

Odd, as I thought if a processor was too overclocked it crashed, as the OS is running on it. I know that GPUs can create errors without crashing if slightly overclocked (you get artefacts on the display).

I tested with primegrid cpu tasks no error. windows 10 running smoothly, no display glinch or lag. CPU temp 55-60 Celsius. GPU-Z shows GPU temp 58 celcius ,load %96. I don't know what cause this.

I was just thinking that maybe, just maybe that some of these posts would be better suited in another thread. Something like the crunching area. Would help others if they have a problem with a GPU card or want to talk about performance of their system. To me it isn't news about the new bundling of work units or new updates being released. Then others can read the title of the thread and see what people are talking about instead of wading through every thread to find something.

Thanks,

Rich

Yeah sucks about the 390 cards not being able to run more than 1 Einstein task.
My 280 was great until it died.

I haven't tried M@H yet because I'll have to try & remember how to change the xml file.

<app_config>

<app>
<name>milkyway</name>
<max_concurrent>0</max_concurrent>
<gpu_versions>
<gpu_usage>0.16</gpu_usage>
<cpu_usage>0.08</cpu_usage>
</gpu_versions>
</app>

<app>
<name>milkyway_nbody</name>
<max_concurrent>0</max_concurrent>
<gpu_versions>
<gpu_usage>0.16</gpu_usage>
<cpu_usage>0.08</cpu_usage>
</gpu_versions>
</app>

<app>
<name>milkyway_separation__modified_fit</name>
<max_concurrent>0</max_concurrent>
<gpu_versions>
<gpu_usage>0.19</gpu_usage>
<cpu_usage>0.08</cpu_usage>
</gpu_versions>
</app>

</app_config>

To be fair, it's easier watching multiple things at once with the progress bar resetting. The only reason I see for changing this is for aesthetics, not serving any practical purpose that I'm aware of. Maybe to help avoid some confusion, though on the other hand it might also help illustrate how the WUs are running to people who aren't aware of them being bundled in this way.

I understand some people prefer form over function though... ;)

I'll make do either way.

Cheers, guys.

I prefer function over form actually, and to have a progress bar that moves back and forth is illogical.

It doesn't exactly follow the rules of expectations, if that's what you mean, but I'm not sure that it necessarily should, given that it isn't actually just running one WU, but running several one at a time separately from each other.

But as it's only 1 bar trying to show 5 things, it just makes a mess. When it says 35%, that could be any number of positions.

I agree that that aspect of it doesn't make much sense if you're tying to see at a glance when the whole WU will end.

It doesn't make sense in any way. If you see it reading 5%, where is it? You have no idea which of the bundle it's working on. If it only passes once, then you know it's a quarter way through the first one.

To be fair, it's easier watching multiple things at once with the progress bar resetting. The only reason I see for changing this is for aesthetics, not serving any practical purpose that I'm aware of. Maybe to help avoid some confusion, though on the other hand it might also help illustrate how the WUs are running to people who aren't aware of them being bundled in this way.

I understand some people prefer form over function though... ;)

I'll make do either way.

Cheers, guys.

I prefer function over form actually, and to have a progress bar that moves back and forth is illogical.

It doesn't exactly follow the rules of expectations, if that's what you mean, but I'm not sure that it necessarily should, given that it isn't actually just running one WU, but running several one at a time separately from each other.

But as it's only 1 bar trying to show 5 things, it just makes a mess. When it says 35%, that could be any number of positions.

Discriminating against failed WU or similar does make more sense to me though as that might gunk up the works a bit, even though I might technically fall under this category for the time being. I can assure you that isn't my intent. Hopefully my comments in this thread have helped shed some light on these issues as well.

Pointing fingers doesn't solve the problem. My computer has done a lot of good work for this project, and as mentioned, has been within the top 5 performing hosts in the not too distant past. Off the top of my head, I think it got up to 4th place, but had been within the top 10 for a few months. I hope to get it back up there again after I get these issues sorted out.

Lol. :) I wasn't talking about you at all.
I was talking about (100% or almost 100% invalid or errored tasks):
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=606779&offset=0&show_names=0&state=5&appid=
(50k invalid tasks in 2 days)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=23432&offset=0&show_names=0&state=6&appid=
(2k invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=698232&offset=0&show_names=0&state=5&appid=
(3k+ invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=586986&offset=0&show_names=0&state=5&appid=
(3k+ invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=694659&offset=0&show_names=0&state=5&appid=
(2k+ invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=630056&offset=0&show_names=0&state=6&appid=
(almost 2k invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=259168&offset=0&show_names=0&state=6&appid=
(almost 2k invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=706643&offset=0&show_names=0&state=6&appid=
(almost 2k invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=709083&offset=0&show_names=0&state=6&appid=
(almost 1k invalid tasks)
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=637080&offset=0&show_names=0&state=5&appid=
(500 invalid tasks)

Those Hosts don't really generate ANY credits.
And those are just from 15 of my "can't validate" WUs. So there are many more of those...
My personal favorite is Hosts that have a limit of 10k Tasks per day, and somehow receives more than 20k. After a single day, "Max tasks per day" should drop to 100, unless SOME WUs are correctly returned.
Some time ago I have created a thread:
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3990
which was "ignored" by the community, so "we" weren't interested in server performance. And I suspect that this time it will be similar.

Bonus points since it was the SAME HOST, that currently gives us 20k invalid results per day.

To be fair, it's easier watching multiple things at once with the progress bar resetting. The only reason I see for changing this is for aesthetics, not serving any practical purpose that I'm aware of. Maybe to help avoid some confusion, though on the other hand it might also help illustrate how the WUs are running to people who aren't aware of them being bundled in this way.

I understand some people prefer form over function though... ;)

I'll make do either way.

Cheers, guys.

I prefer function over form actually, and to have a progress bar that moves back and forth is illogical.

Hey Everyone,

Sorry for the silence yesterday, I decided to take a day off yesterday to recharge a bit after the huge push I've been doing for the last two weeks. I will be working on the Linux GPU apps today, the Mac applications, and if I have time I will look into fixing the cosmetic issues with the progress bar.

Jake

Jake,

I hope that Fixing issues with "Max tasks per day" will come next.
There are at least a dozen Hosts that spam server with Invalid tasks, and process over 10000-20000 Tasks every day. They also cause some problems with creating Invalid WU. Thus, some of our work is wasted.
IMHO this parameter can start at a lower numer and grow linearly as valid Tasks are generated.

As for the cosmetic changes, I actually rather like being able to easily see on the progress bar when one of the bundled tasks ends as it's helping me to troubleshoot some issues I seem to be having on my end (see my last couple posts), being able to monitor bundled task progress, CPU load, and GPU load in real time. But hey, that's just me.

Yes it is just you :-P
I'd like to see the progress of the whole WU.
Since there are 5 in the bundle, you can just watch for 20/40/60/80/100% :-)