Subject: Re: BOINC migration...
From: sideband
Date: 12/11/2004, 08:52
Newsgroups: alt.sci.seti

Derek:

Thanks for the reply.

There's more involved than what I initially posted, and I should have been more specific, I'm sure.

Let me explain.

Right now, I like the original system. I have SetiQueue running to track my clients, making sure they're still up and running, etc. It's a great tool for caching workunits and monitoring performance. I like to be able to pull up a browser and see how things are doing on all the machines I have running SETI@Home.

I changed email addresses on the original SETI@Home apparently after my stats and account were migrated to BOINC. I can't access my old stats on BOINC, so if I migrate to BOINC, it'll be like I'm starting over, and I don't want to do that, either.

I like the idea of a binary that runs in the background, that I can monitor with SETI Spy, as well. Another great program that's proven invaluable in comparing stats on different system settings, hardware, etc.

BOINC offers nothing to me except a client I have little control over, little caching, loss of my stats, and a lack of centralization on a local level (in my intranet).

Unless I'm missing something...

It would be nice if the descriptions of BOINC on the web were a bit more concise, so I knew for sure what I was getting into.

Is the BOINC client supposed to run faster than the old 3.08 clients?

Is there a way to monitor all my clients on my localnet from one machine, such as SetiQueue allows me to do?

Are these other machines I have going to be supported under BOINC? For example, the Arch/OS combinations I noted in a previous message in this thread. NetBSD/i386, NetBSD/Alpha, NetBSD/Sparc, NetBSD/Sparc64, Linux/Sparc, Linux/Sparc64, and Linux/Alpha.

Whenever Berkeley came out with a new binary to run for a particular arch, I did much comparing of that client with the old client, and the new client against itself on different OS's under the various compat codes available. I've found that the Windows client runs faster under WINE on Linux than it does on the same machine under Windows, but the fastest combination I've found is the Linux client running under compat_linux under NetBSD 1.6.2. The fastest Alpha client under "classic" was the Alpha Linux client running under compat Linux on NetBSD 1.6.1.

I like to play with performance data, and tweak things to get the most out of the systems I have running. I don't see where BOINC is going to allow me to do this easily.

I used to post here alot, back in '99, 2000, and 2001. Most probably don't remember me, but I was the unfortunate cause of much debate because of my findings. We got it ironed out, but you know it's all for science.

Is BOINC going to allow me to do this, on all my platforms?

When it does, I'll migrate. It's an all-or-nothing proposition for me. If I'm going to compare performance, it needs to be on the same "platform".

Thanks for any input you might have.

73 de AI8W, Chris

AKA, "SideBand" and "-SSB"


Derek Lyons wrote:
sideband <AINO8SPAMW@cac.net> wrote:


If I move to BOINC it will bring a full third of my SETI farm down...


So, do a partial migration.  Move the machines that have a version of
BOINC available over to BOINC, and leave the remainder running
Classic.  (FWIW, you can run Classic and BOINC on the same machine,
just ensure niether is set as the screen saver.)

Also, there may be uses for the machines that cannot run BOINC such as
primenet, etc..

D.