WARNING: This website is obsolete! Please follow this link to get to the new Albert@Home website!

Posts by TRuEQ & TuVaLu

1) Message boards : Problems and Bug Reports : FGRP application v 1.07 (OPENCL) feedback thread (Message 112549)
Posted 20 May 2013 by TRuEQ & TuVaLu
Post:
On my computor with 1 PCIE lane X4(5850) and 1 lane X16(5970(2GPU)
I've noticed a difference in performance by something like 20-30%

I believe the app is using alot of PCIE transfers and that is why the PCIE X16 is alot faster. Less PCIE transfers would be good for this app in the future.

I also made some more testing.
I found no problem runing 2 instances of app on each GPU

I use app_config.xml file to do that.
I ran app(2) on 2GPU's all night.
No problem detected.

And.

I only ran them on the 5970 card since it is PCIE1.1 X16 and faster for the app.
When running 2 at a time , max 4 on 2 of 3 gpu's I saw that SIV graph loks as it should. It might have to do with me change driver to 12.10 from 12.8, I am not sure yet. I'll try some more.



And I also have a 6670 card with a I7 Intel computor.
That is PCIE2.0 X16 and that is even faster. 10-20%
That may proove the PCIE speed of app theory.

https://albert.phys.uwm.edu/results.php?hostid=7377

That is all for me for now.
Tanks for a great app.

//TRuEQ
2) Message boards : Problems and Bug Reports : FGRP application v 1.07 (OPENCL) feedback thread (Message 112537)
Posted 18 May 2013 by TRuEQ & TuVaLu
Post:
I made another SIV picture for reference.
3gpu tasks from Distrtgen are running.



I'd say optimal temps for 5850 is between 70-74 degrees C , at max load
And for the dual GPU card 5970 is between 88-93 degrees C , at max load

3) Message boards : Problems and Bug Reports : FGRP application v 1.07 (OPENCL) feedback thread (Message 112536)
Posted 18 May 2013 by TRuEQ & TuVaLu
Post:

I have a SIV picure that shows how it looks.



I saw in post in previous version that similiar thing was found.


Hmm.. that stuff looks odd. The card with the highest load according to the diagram over a timeline has a low temperature, while another GPU with only intermittent load has a very high temperature, and the second GPU doesn't have a temperature reading at all, even tho all GPUs are very similar (Cypress GPU). So I'm not quite sure which part of the data from this tool can be trusted, because there are obvious inconsistencies.

Cheers
HB


Temps are easily explained.

The ATI 5850 has a manual setting of 76% of fan speed, and a not soo good gpu chassi construction. It's cooling are not the best.

The 5970 has a great gpu chassi construction which allows the airflow to come into the card and out of the computor chassi's back.
The fan is also stronger since there are 2 GPU's in 1 card which makes the 5970 alot warmer then the 5850.

Theese are the idle temps.



The low graphs in SIV are verified with GPU-z for each card.



4) Message boards : Problems and Bug Reports : FGRP application v 1.07 (OPENCL) feedback thread (Message 112533)
Posted 17 May 2013 by TRuEQ & TuVaLu
Post:
I also got this from another programmer.
Can it be of use here?



"As I recall BOINC uses ADL_Adapter_NumberOfAdapters_Get () and ADL_Adapter_AdapterInfo_Get() to get the list of GPUs."

5) Message boards : Problems and Bug Reports : FGRP application v 1.07 (OPENCL) feedback thread (Message 112532)
Posted 17 May 2013 by TRuEQ & TuVaLu
Post:
I am not sure that the GPU load is correct.
I run 3 tasks, 1 on each GPU.
I have:

gpu(0) ATI 5850
gpu(1) ATI 5970 ; first gpu
gpu(2) ATI 5970 ; second gpu


I have a SIV picure that shows how it looks.



I saw in post in previous version that similiar thing was found.
6) Message boards : Problems and Bug Reports : [New release] BRP app v1.28 feedback thread (Message 112173)
Posted 12 Aug 2012 by TRuEQ & TuVaLu
Post:
I did 1 task.

http://albert.phys.uwm.edu/results.php?hostid=3755

Was faster then the older one.

Good work.
7) Message boards : Problems and Bug Reports : [New release] BRP app v1.23/1.24 (OpenCL) feedback thread (Message 112069)
Posted 10 May 2012 by TRuEQ & TuVaLu
Post:
I am now running 1 albert task on my ati 5850 with 0.932cpu and 1 seti ap task on the same gpu

I also noticed 2 cpu tasks running at the same time on my 2 cores.
1 of the cpu projects runs fully on 1 core and the other cpu project runs on the albert core with 0.1 cpu

I cannot be sure that the cpu cores use different cores though...
I lack the knowlegde in how to pursue the threads.
My conclusion is that I know have 1 cpu project running with 0.1 cpu on the same core that feeds the GPU for albert.

Any chance if this is correct that you can free some more % from albert task that runs? Albert only uses below 50% of 1 cpu core.
8) Message boards : Problems and Bug Reports : [New release] BRP app v1.23/1.24 (OpenCL) feedback thread (Message 112068)
Posted 9 May 2012 by TRuEQ & TuVaLu
Post:
I don't know if this is a BM thing or albert app thing.
But the downloaded tasks shows an estimated runtime of 20hours and they all get done with about 1-2hours.
I use BM 7.0.27
All other projects adjust as they should....Except POEM@Home that sometimes show strangly numbers....
Have I run to few tasks??
9) Message boards : Problems and Bug Reports : [New release] BRP app v1.23/1.24 (OpenCL) feedback thread (Message 112064)
Posted 9 May 2012 by TRuEQ & TuVaLu
Post:
I must add this:

When running a cpu project on 1 core and albert gpu task starts then the cpu project goes into "waiting to run state".

Any chance that you can make albert GPU task work so it is a GPU task and not as it is now a cpu task??
10) Message boards : Problems and Bug Reports : [New release] BRP app v1.23/1.24 (OpenCL) feedback thread (Message 112063)
Posted 9 May 2012 by TRuEQ & TuVaLu
Post:
I've ran a few tasks with 1.24 and it looks fine.

60%-70% GPU usage and 0.932CPU but it doesn't use more then 40% and has an avg cpu usage of 25%.

It works well with the 0.5 option and is able to run alongside Milkyway SETI POEM and Primegrid without a problem.
11) Message boards : Problems and Bug Reports : [New release] BRP app v1.23/1.24 (OpenCL) feedback thread (Message 112061)
Posted 8 May 2012 by TRuEQ & TuVaLu
Post:
ATI 4850(512MB) no tasks.

ATI 5850(1024) running with 0.94cpu and 0.5gpu alongside a milkyway task.
progress of task is 44% and ticking.
12) Message boards : Problems and Bug Reports : [New release] BRP app v1.23/1.24 (OpenCL) feedback thread (Message 111979)
Posted 27 Apr 2012 by TRuEQ & TuVaLu
Post:
I made an answer in another thread that also migth be in here.

http://albert.phys.uwm.edu/forum_thread.php?id=8883&nowrap=true#111976
13) Message boards : Problems and Bug Reports : GPU utilization factor (Message 111976)
Posted 27 Apr 2012 by TRuEQ & TuVaLu
Post:
The first task which I am running before change to .05 is still showing 1.0
First task was started with setting GPU 1.0
Second task started with setting 0.5

But the other shows running 0.5GPU's



I am running 2tasks simultaniously now.
ATI 5850 CAT 12.3 BM 7.0.26

:)

It uses Both my cores so I have no CPU% left for other tasks.
Windows task manager says each task is using about 20% so if that could be modified to the app, that would be great.
I think SETI Beta is now using some way of <flops> calculation to set the CPU % before tasks is started.
14) Message boards : Problems and Bug Reports : [OpenCL] app v1.20/v1.21 feedback thread (Message 111796)
Posted 2 Feb 2012 by TRuEQ & TuVaLu
Post:
As I said, we can reduce it but only by dropping OpenCL 1.0 (i.e. AMD 4xxx) support.

Oliver


Ok
15) Message boards : Problems and Bug Reports : [OpenCL] app v1.20/v1.21 feedback thread (Message 111794)
Posted 2 Feb 2012 by TRuEQ & TuVaLu
Post:

I run on an ATI 4850 with 512MB RAM and Catalyst 11.12


As discussed earlier, we (still) need ~490 MB free GPU memory. This does't seem to be the case here. We'd be able to reduce that by 120 MB but that would mean to exclude all OpenCL 1.0 GPUs, including your 4xxx series card.

FYI, we think about doing this anyway since the OpenCL 1.0 devices don't offer a significant performance gain over the CPU version so it seems worthwhile dropping their support in favor of more relaxed memory requirements.


Cheers,
Oliver


Well, if the mem need was 450Mb you would have a few more 4xxx cards....
I think that my card has about 480Mb free so if the demand is 470MB one could run the app on 48xx cards.
16) Message boards : Problems and Bug Reports : [OpenCL] app v1.20/v1.21 feedback thread (Message 111792)
Posted 2 Feb 2012 by TRuEQ & TuVaLu
Post:
Hi, I have some tasks that all gave errors.

http://albert.phys.uwm.edu/results.php?hostid=1353&offset=0&show_names=0&state=5&appid=

I run on an ATI 4850 with 512MB RAM and Catalyst 11.12
BM 7.0.12
17) Message boards : Problems and Bug Reports : Wrong estimates of "Remaining" time (Message 111768)
Posted 27 Jan 2012 by TRuEQ & TuVaLu
Post:
Using the anonymous platform is a bit too steep a thing to expect from a new user. It's even a steep angle expected from a normal user. And even advanced users don't get everything right the first time around.

Put <flops>209876543210</flops> into the file and then adjust it if it turns out to be very wrong.

Right, so you just add an imaginary number and go adjust that in case it doesn't work. Where's the science in that? it also makes all of BOINC a hands-on experience, with you having to exit BOINC tingle with some files and restart BOINC for every task, or else the TDCF will be out of whack again. Which it will be anyway, when a new application is released and the resource flops estimate is not completely correct.

But all that aside, it would be nice if there was an easy way to calculate the flops value of every piece of hardware you have in your computer. Because it's not just the flops value for the GPU that you need here, but also that for the CPU.

There's 11 different GPUs used on this project alone, that means 11 different flop values for those GPUs alone. Added to that there are a lot more different CPUs on this project. Are you starting to see the problem?

And that's outside the people who have e.g. 8 different GPUs in their system plus a 12 core CPU with HT. I'd love you see help them all to the correct values... forget sleep, forget food, forget family, forget friends, forget TV, you're needed here, 24/7/365.


Well, if there already exists differen't app_info.xml files out there and the people who has them can share them and their experience to new people.
I think there will be alot of people that can help eachother with all the different configurations that is needed.

And, I say it again about the "<flops>209876543210</flops>" estimated.
I use that when a task is downloaded and it shows a dramatic difference in the real time to task completion to get it aproximately right. It will not be correct, but you can come very close. That works fine for me.

And When started to use Computors in 1983 I had noone to show me how it worked.
I got copied printer paper with the code to be programmed so I could run some simple games.
After have typing in several 100 of pages I started to "manipulate" the original programs by changing variables to see how it worked.

I would say the cc_config.xml and app_info.xml are good ways to learn how programs work and can be altered.

The use of a computor shouldn't be just push a button and start a browser by clicking a mouse to start shoping and send simple messages to people.

A computor is alot more then that.
18) Message boards : Problems and Bug Reports : Wrong estimates of "Remaining" time (Message 111766)
Posted 27 Jan 2012 by TRuEQ & TuVaLu
Post:
I forgot....

There isn't any app_info.xml for Albert yet....Or???
19) Message boards : Problems and Bug Reports : Wrong estimates of "Remaining" time (Message 111765)
Posted 27 Jan 2012 by TRuEQ & TuVaLu
Post:
Addendum to what Gary said, it's even more difficult to calculate the progress bar.

- Some projects run work in 15% segments, quickly going to 90% before sitting there literally for hours seemingly doing nothing. (most projects using Autodock have this problem)
- Some projects run in 2% increments. The Gamma Ray application at Einstein will do this.
- Some projects will run to 100% and over it for several minutes. Einstein's Gravitational Wave S6 app will do this continuously.
- And then there's at least one project that runs to 100%, resets to zero and starts again. Enigma.
- Nothing said about the various wrapper apps with their own weird things out there.
- That topped off with invariable run times just amongst applications. Seti runs high angle, low angle and normal angle ranges, all that work runs at varying lengths of time. The devs there can't see when they split the work what is what, so it's astronomically impossible to give them correct flop numbers.

As you can see, if it were so simple as you state, someone would've used it already. :-)



There is always the app_info.xml possibility to adjust the flops.

Put <flops>209876543210</flops> into the file and then adjust it if it turns out to be very wrong.

Like an seti ap task have "remaining 24h",when the actual task takes 2h to complete. Then adjust the flops *10 and you will get closer to th real value.

It still is an aproximation, but when differences is very big it can be of help.
20) Message boards : Problems and Bug Reports : Running on ATI (Message 111739)
Posted 23 Jan 2012 by TRuEQ & TuVaLu
Post:

I think you could have use of ATI/AMD Catalyst driver 11.12 or 12.1 for your 69xx card.


Hi,
not really, there are big problems coming up with the new drivers.
On my AMD-System I've upgraded to newest Catalyst driver and BM 7.0.11 with the effect, that collatz is no longer running. Seti has rarely Astropulse wu's for AMD and the memory on my AMD-card is too small for Albert ATI open-cl apps.

On my other system I run older drivers and older BM to be able to run MW, this project needs drivers < 11.10

An intresting fact is, that with the new HD7970 one can run the nVidia OpenCL-app, faster than the CAL-app on HD6970, without the need of latest BM. 6.12.34 is good for that ...

So, after upgrading to latest available versions I have a GPU running dry. It's really a mess with these versions and requirements.


Yes, it is a mess with the drivers, I agree on that.
And Collatz is thinking of do an Open-Cl app too, but it will be slower then the old app they say.




Next 20



This material is based upon work supported by the National Science Foundation (NSF) under Grant PHY-0555655 and by the Max Planck Gesellschaft (MPG). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the investigators and do not necessarily reflect the views of the NSF or the MPG.

Copyright © 2024 Bruce Allen for the LIGO Scientific Collaboration