ATI AstroPulse released |
![]() |
| log in |
Message boards : Number crunching : ATI AstroPulse released
1 · 2 · 3 · 4 · Next
| Author | Message |
|---|---|
|
There are new ATI AstroPulse apps with much improved performance and CPU utilization available @Lunatics site: | |
| ID: 1032880 · | |
|
Files: What is the difference between these two? ____________ Damsel Rescuer, Kitty Patron, Raccoon Friend, Uli Fan, Julie Supporter, ES99 Admirer, PETA Member, 1st Childhood | |
| ID: 1032970 · | |
First uses OpenCL only, second uses Brook+ FFA from older hybrid build. For some configs second approach can be faster (or more reliable), for anothers - pure OpenCL will go better. So I provide both. On my own host r449 performs slightly better than r456 with default settings. From other side, r456 has 2 tunable parameters for FFA - some area for further "inplace optimization " by user. | |
| ID: 1032992 · | |
|
что то я не догоняю, статус сервера показывает что задания для АР есть, а мне выдает: | |
| ID: 1033017 · | |
First uses OpenCL only, second uses Brook+ FFA from older hybrid build. Thanks. appreciated. ____________ Damsel Rescuer, Kitty Patron, Raccoon Friend, Uli Fan, Julie Supporter, ES99 Admirer, PETA Member, 1st Childhood | |
| ID: 1033023 · | |
что то я не догоняю, статус сервера показывает что задания для АР есть, а мне выдает: Посмотри на загрузку сети: http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-250/gigabitethernet2_3;view=Octets;ranges=d:w Канал сейчас битком, а отправить можно только задания, которые лежат в оперативке на сервере (куда меньше чем в принципе готовых, что на странице написано статуса). Просто сейчас очень много народа пытается загрузить, сервера до завтра (а то и послезавтра) перегружены будут. | |
| ID: 1033027 · | |
|
ясно, спасибо | |
| ID: 1033037 · | |
|
OK, I have downloaded the zip file and extracted to the seti project folder, and added the extra lines from the lunatics site into the end of the app_info file and rebooted Boinc. All came up ok without any errors. I noted there was already an AP 505 entry, does that remain or is it taken out? | |
| ID: 1033038 · | |
OK, I have downloaded the zip file and extracted to the seti project folder, and added the extra lines from the lunatics site into the end of the app_info file and rebooted Boinc. All came up ok without any errors. I noted there was already an AP 505 entry, does that remain or is it taken out? AFAIK now, there can be few same <app></app> sections. But having one <app> section for AstroPulse and few different <app_version> sections is OK too. In short, if BOINC didn't complain in message tab about parsing errors or some missed files, very probably that all OK :) | |
| ID: 1033040 · | |
|
I was in the process of writing these questions when the beginning of the major air condition outage struck. They were very fresh then, and (after editing down a few, mostly still interesting, at least to me). | |
| ID: 1033323 · | |
The _ncpus values are only used for task scheduling in the core client. For a single GPU system it's fairly simple, anything less than 1 means the client won't reserve a full CPU to support the GPU. After you've observed actual usage using Task Manager you might want to edit the values to reflect that, just as preparation for possibly adding another GPU later, etc. If there are no <flops> entries at all, the core client uses the CPU Whetstone benchmark for both CPU and GPU. If there's no <flops> for the CPU applications, the <flops> for the GPU ought to be somewhat higher than the CPU's Whetstone benchmark for most hosts. If you want to run that way you might start with something like 5 times the whetstone benchmark, probably something in the 16 GFLOPS range as Raistmer is using. The best thing for a host which hasn't yet accumulated 10 validated tasks for either CPU or GPU (so it's still getting unscaled estimates) is to put in <flops> for both and force DCF to 1.0, adjusting the <flops> based on the actual runtimes of some of those initial tasks. With DCF near 1.0, when the scaled estimates start arriving there shouldn't be a sudden mix of some tasks with reasonable runtime estimates and a large overfetch of others with very short runtime estimates. 3. Are we naive users who have not run GPU before and may set a wildly wrong flops value in danger of massive over-downloading initially? Any suggested precautions for avoiding that? (such as setting an extremely small sum for the internet connection interval plus additional days work of e.g. 0.001). Only if someone believes that the advertised speed of the card is achievable in real life. Yes, setting a very small cache would obviously help ensure there isn't an initial overfetch. The other danger of setting <flops> too high is that it makes the elapsed time limit very small and may cause -177 errors. That way each 8 MB downloaded task might error out rather than be allowed time to complete normally, bad news for both the user and the project's bandwidth. 4. Are we naive users who run multiple projects in danger of greatly unbalancing SETI vs. other project workload (perhaps by setting inappropriate flops number) initially? Suggested ameliorative actions? Getting <flops> set correctly stabilizes DCF and the core client has a sensible basis for work fetch and sharing resources with other projects. 6. I believe that if I first ran my queue to zero, then did a correct install for one of these new ATI/Astropulse aps, but removed the other ap sections in my ap_info, I would receive only Astropulse downloads from SETI. Is that right, and is there any good reason not to? {edit: in the event I did run down my queue to zero, and currently have an ATI-only ap_info. When work becomes available again I can comment on how that worked). Yes, the BOINC servers won't send work to an anonymous platform host unless it claims to have an application to do the work. I won't try to answer 7. Joe | |
| ID: 1033354 · | |
7. I never game, and my new host has a fanless HD4550 card. I have decent case cooling support for it (an 800 rpm 120mm fan in a side port right over it, and no other add-on cards with power dissipation above the nuisance level). Am I in danger of greatly exceeding the previous temperature of my GPU? Any practical suggestions of monitoring tools, throttling methods, and practical temperatures of concern. I have and plan to watch GPU-Z. It reports 60C with 0% reported workload now, though the actual metal cage over the fins is only warm, not painfully hot. Try TThrottle for automatic Temperature regulation or some of the other Temperature Monitoring Programs: http://setiathome.berkeley.edu/forum_thread.php?id=59292 ____________ - ALF - "Find out what you don't do well ..... then don't do it!" :) | |
| ID: 1033430 · | |
I'm not prepared to discuss flops values in full, better refer Richard's thread about setting flops. (sticky one) Listed value was recived by adjusting estimations for my own host (Q9450+ATI HD4870). Currently I have pretty correct estimations and no -177 errors. IMO for first attemt same value can be used. For reference HD4870 should complete AP task (not heavely blanked one) in less thsn 5 hours. If your time estimation greatly exceed this value you should increase flops. If estimation much lower - decrease flops. HD5xxx GPUs tend to work faster in spite of no 5xxx-special features used. And one more note about this app - there can be no compatibility with CPU stock/opt app by checkpoints. That is, better not transfer already started tasks between CPU and GPU. Sometimes it will resume just OK, sometime it will fail or produce invalid results. I have no intentions to maintain checkpoints compatibility in future too cause GPU build just don't need most of data saved in CPU checkpoint and writing that data to GPU checkpoint will introduce unneeded overhead. | |
| ID: 1033471 · | |
I have some extremely naive first-time GPU-user type questions. Possibly bad form to reply to my own post, but I thought it might possibly be useful for me to add some first-time user experience comments to the expert replies already provide by Raistmer and Josef S. Segur. The system is a very recently assembled Windows 7 PC with an E5620 (Westmere) running hyperthreaded. The Graphics card is a Gigabyte GV-R455D3-512I. It is a fanless card which after rebate will have cost me $30. I had not thought of either gaming or crunching with it, but when I saw the processor type on the ATI page of supported types pointed to by the Lunatics page, I decided to give it a try. As specified on the Lunatics page about using these aps, I installed the ATI stream SDK and the Catalyst 10.7 driver set. For ap_info, I made a bare-bones one out of the example posted on the Lunatics page (with the numeric parameters for flops and such left as there), only adding the surroundings required to make it a full ap_info with no other aps specified. My intention was fully to occupy my eight CPU threads with Einstein on this host, and to keep the graphics processor busy with Astropulse work. So far, this seems to be working as hoped. As the first attempts to get an Astropulse WU were made only a few hours into the September 16 recovery, it took the system hours to get granted a unit, and quite a few download retries before it came through, but from there things seem so far to have been smooth. Initially I had left the computing preferences item specifying "Suspend GPU work while computer is in use?" at Yes. Overnight with me not present the job made lots of progress, but with my copy of BOINCMgr (6.10.58) this indeed worked, so the job paused a lot. I've since changed this to "no", and have not yet noticed adverse effect, but on negligible testing. The 4550 is not a high-end implementation at all. (very) preliminary measurement suggests that the added power consumption at the system input plug is in the ten to twenty watt range (full Astropulse vs. idle). The reported GPU temperature rise is about 20 to 25C (highest seen so far about 83C). My card is fanless, but the card location is unusually well ventilated with a 1150 rpm 120mm side fan blowing air pretty directly to its benefit. I harbor a doubt that the sensors are well calibrated (Intel CPU temp sensors are biased all over the lot, have slope errors, and even slope discontinuities, so this would not be unprecedented). 58C is the lowest I have seen, in a cool room, card at idle, with all that fan ventilation, which seems higher than plausible to me. In sum, for my particular case I'm not currently worried about over-stressing the 4550 by 100% use. And the contribution to box thermal problems for me is a non-issue. As to performance, It currently shows as 67.6% done with 8 hours 51 minutes "elapsed" reported by BOINCMgr. [edited to add: The CPU application running to support the ATI card doing the numeric processing appears to be consuming about 5% of one equivalent virtual core, so somewhat under 1% of the total CPU capacity. Others with faster graphics cards and slower CPUs may well see this rather higher--but this is quite nice). Here is a link to a screen capture of what GPU-Z reports about my card for general information: card info And this link gives sensor information, as stabilized running this Astropulse ap at a room ambient of 21C. temperatures, utilization, and clocks GPU-Z describes the fan speed percentage entry as that reported by the on-die controller. As the card is fanless, this may be garbage data. A more optimistic view may be that the controller is only asking for 41% output if it had a fan to control, so does not regard the die temperature as terribly excessive As to power, here are some system power input numbers. The E5620 is running a moderate overclock at 3.4 GHz and 1.14 reported CPU voltage. 236W 8 Einstein Global Correlations + 1 ATI Astropulse 142W 1 Astropulse 128W All BOINC suspended] ____________ | |
| ID: 1033563 · | |
to jsut monitor the GPU temp you can use the GPU-Z app. it works fine. I would consider an aftermarket GPU cooler. Question: have you ran any other project that uses the GPU and have you checked the temps then? Your temps will be similar using the Astropulse app. I'd look into an aftermarket HSF for your GPU ____________ Proud member of TSWB. End terrorism by building a school | |
| ID: 1033659 · | |
|
Not bad. Error in ap_remove_radar.cpp: generate_envelope: num_ffts_performed < 100. Blanking too much RFI? Max GPU temperature, 51C. Max GPU load, ~90%. No slowdown problems as seen with Brook+ apps. Third is downloading as I type. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 1033746 · | |
Max GPU temperature, 51C. Where did you see that? GPU-Z? something else? For your system, what does the same monitoring method give for GPU temperature at idle? The SETI page for your hosts lists the graphics processor as: CAL ATI Radeon HD 4700/4800 (RV740/RV770) (1024MB) driver: 1.4.696 What is the particular product you have? ____________ | |
| ID: 1033763 · | |
For your system, what does the same monitoring method give for GPU temperature at idle? 37C. Tool used: GPU-Z. The SETI page for your hosts lists the graphics processor as:CAL ATI Radeon HD 4700/4800 (RV740/RV770) (1024MB) driver: 1.4.696 HD4850 1GB PCI-E 2.0 Cats 10.7 (why change when it works... ) Apropos, perhaps that the use of 3 x 80mm case fans - one directly above the GPU - does lots to keeping the heat down inside the case. The only dust I have seen on there since I put together the system is on the air-inlet rasters. Surprisingly good at keeping itself dust free so far, considering the amount of furry friends we have around here. :) Edit: before you ask, I just started up CoreTemp, to check the CPU temperature. 55C for core 0, 57C for core 1 (plus same for their HT compadres). ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 1033766 · | |
|
OK, I have to ask. I've seen this behaviour on 2 OpenCL APs now. | |
| ID: 1033985 · | |
OK, I have to ask. I've seen this behaviour on 2 OpenCL APs now. Do you use single GPU or multi-GPU host? Also, check blanking % of task. CPU usage can increase greatly for heavy blanked tasks (cause blanking processed on CPU for now). I got reports about very fast exits due to excessive blanking ~100%. It means current AP tasks are very noisy ones. Not the best example for app capabilities... but we crunch what we get ;) More insights stderr log of completed result could give. | |
| ID: 1033993 · | |
Message boards : Number crunching : ATI AstroPulse released
| Copyright © 2013 University of California |