I have Primegrid as my backup, it is the only backup project that runs on an ATI and I consider to be at least vaguely useful... If you set the resource share to zero, it only makes the project the backup. It does not limit the number of WUs that are downloaded once the backup kicks in. I think backup projects should work the way you describe, but they don't. I checked on the BOINC site. There is no way to force BOINC to only download a single WU at a time.

Sorry, no. I use collatz as backup, I use ATI-Cards, and it's always only one wu that is downloaded.
It depends on the projects server version, but at collatz this feature works perfect.

I finished a WU last night and it went out. Didn't see any changes so THEN I read this post. Am I to understand that task is LOST?

Yes.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

If we increase the cache, then this type of database crash would happen significantly more often. We just don't have a powerful enough server to increase the size of the workunit and result tables that much.

On that note...
This is my idea of a budget (best value/cost ratio) server. All prices are USD, quoted from US retailer Newegg.com on Oct 10, 2011(I do not work for them) I think we as a community could come up with this. I will put up $500 seed money.

I have started a seperate thread for this in the cruncher section. All feedback, especially from those with experience with server configurations, is welcome.

Not Included: Case/mounting hardware, power supply, raid hardware, which are all better left to whoever sets it up.

Qty. Product Description Total Price
1 ASUS KGPE-D16 SSI EEB 3.61 Server Motherboard Dual Socket G34 AMD SR5690 DDR3 800/1066/1333
Item #: N82E16813131643 $429.9

2 AMD Opteron 6128 Magny-Cours 2.0GHz Socket G34 115W 8-Core Server Processor OS6128WKT8EGOWOF
Item #: N82E16819105266 $499.98

16 Kingston 8GB 240-Pin DDR3 SDRAM DDR3 1333 ECC Registered w/ Parity Server Memory Model KVR1333D3Q8R9S/8G
Item #: N82E16820139280 $1,215.84
Though i would discourage it, if we can get by with 64GB, we could save ~$600

2 Mushkin Enhanced Chronos Deluxe MKNSSDCR120GB-DX 2.5" 120GB SATA III MLC Internal Solid State Drive (SSD)
Item #: N82E16820226225 $499.98
System/boot drive. 2x120GB is for possible raid or swap/pagefile. If neither is wanted we could get 1x240 for the same price or just save ~$250

2 Western Digital AV-GP WD20EURS 2TB SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive
Item #: N82E16822136783 $189.98
I don't know if this application needs much local storage, but its cheap.

2 Thermaltake CLS0015 70mm 1 Ball, 1 Sleeve CPU Cooler for AMD Socket G34 1U
Item #: N82E16835106158 $71.98
------------------------
$2,907.75

I have Primegrid as my backup, it is the only backup project that runs on an ATI and I consider to be at least vaguely useful... If you set the resource share to zero, it only makes the project the backup. It does not limit the number of WUs that are downloaded once the backup kicks in. I think backup projects should work the way you describe, but they don't. I checked on the BOINC site. There is no way to force BOINC to only download a single WU at a time.

Sorry, no. I use collatz as backup, I use ATI-Cards, and it's always only one wu that is downloaded.
It depends on the projects server version, but at collatz this feature works perfect.

Actually you are both correct, the difference lies in the BOINC manager version that you are running.

The 6.10.xx series requests a chunk of work and it gets multiple work units.

The 6.12.xx series requests 1 work unit per idle resource.

I have Collatz as my backup project for the HD5830 and it only maintains 1 work unit at a time right now.

---

hm? why? how do you mean that? I have dnetc as backup backup backup emergency energywasting project when SETI Backup offers no Astropulse on the MW Machine. Normaly over BOINC Manager..

You can't just attach to DNETC and Moo Wrapper via BOINC manager.

Then plz explain it to me how i done it with DNETC when you know it that exactly ... ;)

I don't know. It's not listed for me when I go to attach a project.

I guess there was no good news to report today...

---

Much Projects are not listend in there. Thats nothing new ;) Try DNETC.org (or .net) as projectURL. One of them work.

---

DSKAG Austria Research Team: http://www.research.dskag.at

It isn't listed there (that might be a developer choice at BOINC central), but you can attach by this sequence in the BOINC client.

1) Tools
2) Attach to project or account manager
3) Attach to project
4) Type in the project URL:

For Dnet that would be http://dnetc.net/
For Moowraper that would be http://moowrap.net/

I don't know that you can do this via the BOINC account manager side of things though as I attach to projects via the attach to project option.

Then plz explain it to me how i done it with DNETC when you know it that exactly ... ;)

I don't know. It's not listed for me when I go to attach a project.

I guess there was no good news to report today...[/quote]

---

I was following this discussion yesterday, since I completed a nice unit and it went out to you, only to discover belatedly that you were down.

I see the "big" contributors are asking for larger work units. I don't support that at all. I understand computers always have glitches and I'm not mad about no credit, but I'm certainly not interested in using up a lot of time for nothing again. Just saying.

I am gauging the cost of an appropriate server right now.

---

nevermind.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Travis, we had problems in the past then you came with the idea to clear the database very quick, so most of us could not see the results page.
Then there where no more outages, unless airco problem RPI, not your fault.

A few weeks ago you increased the results pages (36 for me some times) this is off course a heavy load on the database and server. If you reduce this again, wouldn't it help?

---

Greetings from,
TJ

Travis, we had problems in the past then you came with the idea to clear the database very quick, so most of us could not see the results page.
Then there where no more outages, unless airco problem RPI, not your fault.

A few weeks ago you increased the results pages (36 for me some times) this is off course a heavy load on the database and server. If you reduce this again, wouldn't it help?

He already has actually.

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2621&nowrap=true#51321

I'm going to have to lower the time workunits are kept in teh database, I think the number was too high and that's what caused the result table to get too large, corrupt and then crash the whole project.

---