Message boards :
Number crunching :
Does AP get priority for download??
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
![]() ![]() Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 ![]() ![]() |
I got MB a couple weeks ago as well. This was when the AP splitter was down and S@H was forced to send out MB to everyone ![]() In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Aurora Borealis ![]() Send message Joined: 14 Jan 01 Posts: 3075 Credit: 5,631,463 RAC: 0 ![]() |
I think that there are a lot of extra AP in the queue because some error out or have been aborted by users. I haven't received many AP that didn't have at least one compute error or abort. They also take much longer to crunch so MB simply get chewed through faster, especially by CUDA, again leaving more AP in the queue. This all makes it look like there is an excess of AP. I don't mind, AP take longer, but do tend to pay better especially with optimized apps. It will probably take a while before a balance is found. Boinc V7.2.42 Win7 i5 3.33G 4GB, GTX470 |
Cosmic_Ocean ![]() Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 ![]() ![]() |
but then all this CUDA stuff came out Not trying to come off sounding mean or offensive, but have you read the part about "if I go to an MB-only venue, I can get my daily quota of MBs without fail"? I don't think the scheduler decides "you don't have CUDA, so no MB for you", I just think there's a minor logic flaw that either hasn't been found yet, or hasn't been gotten to (there's been some database crises to tend to lately). Hopefully the flaw can be discovered and we can go back to the ~25/1 ratio for MB/AP. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 ![]() |
I have a feeling that the code on the server looks something like: if there is work needed on the host and AP work is available and the user has allowed AP work, send it. if there is still work needed on the host and SETI work is and the user has allowed SETI work, send it. if there is still work needed and the host has allowed other applictions than the one he selected, send it. ![]() ![]() BOINC WIKI |
piper69 Send message Joined: 25 Sep 08 Posts: 49 Credit: 3,042,244 RAC: 0 ![]() |
very odd!!! my amd host is crunching away without any problem and i am getting 6.03, 6.08, ap_5.03 branded wu. id say problem is in older boic versions not on the seti servers. |
Cosmic_Ocean ![]() Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 ![]() ![]() |
I have a feeling that the code on the server looks something like: Yeah, somebody (can't remember who out of richard, ozz, or josef) explained the way the logic works for the selected apps in the venue. It was something along the lines of checking the feeder queue for the selected apps, and if either one responds with a non-zero ready-to-send, that app gets sent. Then if you have 'allow for other apps' selected, all three queues (mb, ap, ap_v5) are queried if the initial query was not satisfied. So at some point, having MB selected on a non-CUDA rig gets ignored. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 ![]() |
I have a feeling that the code on the server looks something like: Only if AP is available and you have AP selected. I bet that if you select MB and allow others, you get MB. It might be better if which app were selected first were random. ![]() ![]() BOINC WIKI |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 ![]() |
I have a feeling that the code on the server looks something like: Using the -allapps mode (as I believe this project is still doing), the shared memory between the Feeder and the Scheduler is organized so the kinds of work are interleaved. The Scheduler goes through that in order, so the effect is supposed to produce a mix of work if the host preferences allow. There are 100 slots in that shared memory, if the project hasn't specified weightings for the 3 different kinds of work there are probably 34 slots for S@H Enhanced, 33 for Astropulse, and 33 for Astropulse v5. When the Feeder succeeds in filling the slots (leaving some empty when there are none of the correct type in the DB within reach of its enumeration) it goes to sleep for 2 seconds. My guess is that describes how it's working, so during that 2 seconds the 34 Enhanced WUs are assigned within a fraction of a second, there probably were no or at most 1 AP WU, and for the rest of that 2 second interval only AP_v5 work is available. The other possibility is that some of that Feeder code isn't doing what the comments say it is designed to do. There's too much database-related code in there for me to really analyze it in sufficient detail to know. Joe |
Cosmic_Ocean ![]() Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 ![]() ![]() |
I had to do some digging, but found my previous post in another thread about what happens when I do NNT for a few days and change to MB-only venue: Message ID: 878468 Alright, well with everything working again, I have been able to finally prove something that I've been saying as an unfounded rumor. turns out I was right. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
©2023 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.