Serpentine (Nov 10 2008) |
![]() |
| log in |
Message boards : Technical News : Serpentine (Nov 10 2008)
| Author | Message |
|---|---|
|
Reminder: Tuesday (tomorrow) is a national holiday. We'll be having our weekly outage on Wednesday. | |
| ID: 829100 · | |
|
It sounds like Anakin has gone over to the dark side... | |
| ID: 829107 · | |
It sounds like Anakin has gone over to the dark side... WWEELLLL, Anakin Skywalker is Darth Vader before the dark side... ;) ____________ . | |
| ID: 829109 · | |
|
So that must be why I've been seeing Astropulse less frequently in my queues in the past week-ish. My main cruncher usually has 10-20 of them, and I've got only four right now with a ton of short multibeams in between. | |
| ID: 829207 · | |
So that must be why I've been seeing Astropulse less frequently in my queues in the past week-ish. My main cruncher usually has 10-20 of them, and I've got only four right now with a ton of short multibeams in between. The AP splitters were producing new work until some time on Sunday, now the only results being created are reissues. The change before that was the -allapps Feeder argument, which was turned on Oct. 30. That configuration has a "weight" for the WUs for each app, and the Feeder tries to tell the Scheduler about work in the proprtion implied by those weights. The weight for AP work is apparently higher than the relative production rate of the ap_splitter set vs. the mb_splitter set, so any extra in the "Ready to send" queue was soon exhausted. AP work ended up being sent just as it was created. That is, there was probably one new AP WU and the two associated tasks about every 7 seconds. If your host happened to ask at the right time it would get one AP task, the odds being approximately one in however many (hundreds?) of work requests the Scheduler receives each 7 seconds. Before that Oct. 30 change, the AP work was largely being delivered in bursts such that a host with a large enough work appetite could get several for one request. Joe | |
| ID: 829299 · | |
|
That's right, I forgot about -allapps already. I noticed last week after it was turned on for a few days that the cricket graph looked pretty stable instead of having 95mbit spikes (presumably the AP WUs being DLed) for half an hour at a time. | |
| ID: 829304 · | |
|
So that must be why I've been seeing Astropulse less frequently in my queues in the past week-ish. My main cruncher usually has 10-20 of them, and I've got only four right now with a ton of short multibeams in between. | |
| ID: 829381 · | |
So that must be why I've been seeing Astropulse less frequently in my queues in the past week-ish. My main cruncher usually has 10-20 of them, and I've got only four right now with a ton of short multibeams in between. http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=942 ____________ | |
| ID: 829402 · | |
So that must be why I've been seeing Astropulse less frequently in my queues in the past week-ish. My main cruncher usually has 10-20 of them, and I've got only four right now with a ton of short multibeams in between. Better would be this one, optimized for the Mac and made by Crunch3r. http://www.arkayn.us/mf/ap_4.35-windows_x86_64_sse3.zip ____________ | |
| ID: 829454 · | |
So that must be why I've been seeing Astropulse less frequently in my queues in the past week-ish. My main cruncher usually has 10-20 of them, and I've got only four right now with a ton of short multibeams in between. I don't believe that is a Mac application with windows_x86 in it's name. Less so since Crunch3r's Seti App's page doesn't say he develops for Mac. Even less since the Mac O/S doesn't see it as an executable file. Could be wrong. ____________ | |
| ID: 829545 · | |
|
I think this is the link arkayn intended to provide: | |
| ID: 829558 · | |
|
I was half asleep last night when I posted that, I forgot that I was hosting the windows version. | |
| ID: 829597 · | |
Message boards : Technical News : Serpentine (Nov 10 2008)
| Copyright © 2013 University of California |