I am doing Einstein on my other computer just Einstein and doing Seti on this one. Shall I do Einstein on this one as well. I am think of allowing Seti do do more work on the other computer it used to but it is only doing Einstein at this percise moment. With a fourteen day deadline I managed to do both on the old computer, so fellow readers shall I allow both computers to do both or maybe more.

---

I am doing Einstein on my other computer just Einstein and doing Seti on this one. Shall I do Einstein on this one as well. I am think of allowing Seti do do more work on the other computer it used to but it is only doing Einstein at this percise moment. With a fourteen day deadline I managed to do both on the old computer, so fellow readers shall I allow both computers to do both or maybe more.

If I were you I would join a couple of projects and then you can set the resource amount to what you want it to be for each, but then you always will have work to do.

---

- cJ

I am doing Einstein on my other computer just Einstein and doing Seti on this one. Shall I do Einstein on this one as well. I am think of allowing Seti do do more work on the other computer it used to but it is only doing Einstein at this percise moment. With a fourteen day deadline I managed to do both on the old computer, so fellow readers shall I allow both computers to do both or maybe more.

It'd probably be better to put both projects on both computers with a resource share of 50% -- especially if you're running the latest BOINC client.

That way, when a project goes down both machines will crunch the other project, and the time will be given back to the other project later.

---

I am having trouble have downloaded 4.45 all I get is repair or uninstall, shall I download it again to do Einstein etc?

---

Silly me sorted in out forgot I had to go into manager to attach to new project, so if anyone answers the previous message I apologise for my HUGE mistake. (not thinking correct)

---

One complication is the variable cache sizing -- for Einstein, folks there have suggested a 1 day cycle, for SETI, it seems longer (say 5 days) is better -- but you can't have both. At least what I've been told is that this number is set across the projects.

It'd probably be better to put both projects on both computers with a resource share of 50% -- especially if you're running the latest BOINC client.

That way, when a project goes down both machines will crunch the other project, and the time will be given back to the other project later.

---

One complication is the variable cache sizing -- for Einstein, folks there have suggested a 1 day cycle, for SETI, it seems longer (say 5 days) is better -- but you can't have both. At least what I've been told is that this number is set across the projects.

Some Boinc projects haven't updated their server software for a while. So then you can run with two different entries. Not the main stream projects which are open, but try a project like SZTAKI. I just noticed my daily connect to was still at 0.1 days, while all other projects I connect to are at 1.5 days.

So it doesn't always work. ;)

But yes, E@H and S@H are updated weekly, so they should follow Barry's post.

---

One complication is the variable cache sizing -- for Einstein, folks there have suggested a 1 day cycle, for SETI, it seems longer (say 5 days) is better -- but you can't have both. At least what I've been told is that this number is set across the projects.

Especially on the later BOINC clients, this doesn't matter as much as a lot of people think.

I've a wide range of "connect every 'x'" values, and I'm currently crunching four projects with client 4.72.

If you run a small value, like 0.2 days, BOINC will likely have one work unit from each project. If a project gets ahead on crunching, the long term debt mechanism will effectively stop it until the others catch up.

If you run a large value, like 6 days, you'll get work from all of the projects, BOINC will process work in deadline-first mode and the long term debt mechanism will control fetch to keep things even.

Higher than 7 days will probably stop Einstein from giving you work, but they should simply limit downloads, or raise their deadline (as I've heard they're going to do).

---

Lizz told me I was wrong ... drat, she was right ...

My current setting is 2.0 days. I do like to keep a few work units around. Most of my computers this was no problem. HOWEVER, my slowest machine would get into trouble about every two weeks or so with Einstein@Home ...

So, rule of thumb, shortest deadline divided by number of projects ... though now they have gone to 14 days ... :)

This is actually a bad habit from my days on SETI@Home Classic ... where you HAD to keep a large cache on hand to get over humps ...

---