2 machines idling! Sell me on your DC project!

[n0cmonkey]

I will probably install Seti on my machine machine, but Im not sure what to do with the others.

Machine 1:
Athlon tb 900
512MB pc133
NOT NETWORKED
OpenBSD 3.1 (can run most Linux binaries)
(I think those are the important factors)

Machine 2:
Sun ultra 10
450mhz UltraSPARC II
128MB pc 100(?)
NOT NETWORKED (but it will be networked in the near future, waiting on parts)
Solaris 8

So, what projects dont require a network connection? What projects work well on a Sun? Where do we need the juice? If there is a project that has a linux client, requires a network connection, and is in the middle of a race or something, let me know, the athlon xp will be put to work there for now instead of seti.

Please, lets keep this civil, we may be on different projects, but its still one team.

 

[GeoffS]

heh... many machines idling! Most Tualatin Celerons and P3s, but a growing number of Athlon XPs!

Geoff

 

[n0cmonkey]

Originally posted by: GeoffS
heh... many machines idling! Most Tualatin Celerons and P3s, but a growing number of Athlon XPs!

Geoff

And hopefully Ill have the dual p3 up sometime in the next week or two. And if this job offer comes through, all machines will be networked sometime next month (hopefully)! So hopefully members start replying and letting us know what our options are and why we should go with their project

 

[Confused]

OK, i'm gonna go for the hard-sell with Seti (providing while they're not networked u can do a bit of work )

You can run Seti and "sneakernet" the work units, using a floppy disk or zip disk etc Others, who have done this, can give advice later

Once they are networked, a SetiQueue would be the easiest

This will provide a central location to upload/download work, and will allow you to keep an eye on the computers, and u can see if a machine is down etc, due to it not uploading results etc

The Athlon XPs will ROCK at Seti, as do faster P4s (cos of the high CPU speeds). The P3s are quite equal clock-for-clock with the Athlons


Confused

 

[n0cmonkey]

SetiQueue either requires a Windows machine or WINE..

 

[Shuxclams]

SETIStacker DOWNLOAD is a caching program for Linux. I believe it was written for BASH but it says it should work with other shells as well. So what next?
There is this as well SETI@HOME Proxy (Java) DOWNLOAD page This should work on any *NIX variant shouldnt it?











SHUX

 

[n0cmonkey]

Originally posted by: Shuxclams
SETIStacker DOWNLOAD is a caching program for Linux. I believe it was written for BASH but it says it should work with other shells as well. So what next?

SHUX

Surprisingly enough I have BASH installed. Probably because I was having trouble with some scripts transferring form sh to bash.

 

[DJSnairdA]

My vote is for SETI!

With SETI2 over the horizon, why not!

 

[Poof]

Not that many projects have OpenBSD or Solaris clients other than SETI and Dnet's OGR. As for Setiqueue... I don't even think it worked with WINE either, although I haven't tried the latest Setiqueue with WINE. There is another queuing program called JSetidoor, which supposedly works pretty good although I haven't tried it. It is a Java app which should pretty much run on any platform with Java installed.

 

[m0ti]

Well take DF into consideration (for the future).

I'm not going to try to sell you on sneaker-netting it though.

When you get 'em networked though, give us a look.

I'm also developing a queue program for uploading results (there already exists a daemon for updates on the download side), so when that's ready, you can use 'em with sneaker-net or internet.

 

[Insidious]

Why drift off into oblivion with a team whose output eclipses your own and makes you feel like a small insignificant speck ???

Come rocket up the charts with Distributed Folding.

You'll get noticed and we provide discrete company for the evening for those who really have a hard time finding a date

 

[ys]

My 450mhz UltraSparc II with 1gig RAM at work takes between 16-19hrs to process a SETI WU. So you might want to look at other projects for it. I've never taken the time to see how other projects perform on the sparc. When you are in a race, every WU counts

 

[n0cmonkey]

Originally posted by: Insidious
Why drift off into oblivion with a team whose output eclipses your own and makes you feel like a small insignificant speck ???

Come rocket up the charts with Distributed Folding.

You'll get noticed and we provide discrete company for the evening for those who really have a hard time finding a date

This was soooo like a commercial its scary!

Im running seti on the athlon xp right now. Job stuff is looking up, so the network could be ready in the near future. I think Ill run a few different clients on the different machines. I cant decide which one to devote all my cycles to

 

[Mucman]

Originally posted by: Poof
Not that many projects have OpenBSD or Solaris clients other than SETI and Dnet's OGR. As for Setiqueue... I don't even think it worked with WINE either, although I haven't tried the latest Setiqueue with WINE. There is another queuing program called JSetidoor, which supposedly works pretty good although I haven't tried it. It is a Java app which should pretty much run on any platform with Java installed.

I've installed JSetiDoor and got it to work (under FreeBSD)...

 

[n0cmonkey]

Originally posted by: Poof
Not that many projects have OpenBSD or Solaris clients other than SETI and Dnet's OGR. As for Setiqueue... I don't even think it worked with WINE either, although I haven't tried the latest Setiqueue with WINE. There is another queuing program called JSetidoor, which supposedly works pretty good although I haven't tried it. It is a Java app which should pretty much run on any platform with Java installed.

The Linux clients for eccp and seti worked just fine on OpenBSD under Linux emulation. Seti has an OpenBSD client right now. If I can get one of the frontends to work Ill see if there is much of a difference in speed. According to the setiqueue site, the latest version works just fine under wine, or they have a WINe compatible version, one of the two.

 

[m0ti]

Oops, just read through my post.

Should read that when the prog is ready you won't need to sneaker-net at all (unless none of your machines have internet access, in which case you can gather all the uploads in a single file at one location, transfer them to a computer with internet access, and upload them).

 

[Poof]

Okay - I thought I had heard somewhere that the newest Setiqueue worked with WNE so one of these days I might trying putzing with it... Also good to know about JSetidoor and a *BSD. I have an older version (1.4.1) of NetBSD that is running OGR right now but I may putz with that too...

I do know that the clients for Sparcs sortof suck... I am running a sparc Linux SETI client on my sparc IPX (it just uploaded a WU this morning) and it takes ~16 days/WU.

The only non-wintel SETI client that seems to run semi-okay for times are the ones for alpha. My 21164/433 MHz is doing WUs in a range of 8:45hrs - 10:15hrs depending on AR.

 

[n0cmonkey]

Originally posted by: Poof
Okay - I thought I had heard somewhere that the newest Setiqueue worked with WNE so one of these days I might trying putzing with it... Also good to know about JSetidoor and a *BSD. I have an older version (1.4.1) of NetBSD that is running OGR right now but I may putz with that too...

I do know that the clients for Sparcs sortof suck... I am running a sparc Linux SETI client on my sparc IPX (it just uploaded a WU this morning) and it takes ~16 days/WU.

The only non-wintel SETI client that seems to run semi-okay for times are the ones for alpha. My 21164/433 MHz is doing WUs in a range of 8:45hrs - 10:15hrs depending on AR.

Isnt the IPX like 25mhz sparc4c? That could be one of the reasons it takes so long

But yeah, so far I havent heard a good word about pretty much any of the projects on SPARC...

 

[Poof]

Originally posted by: n0cmonkey

Isnt the IPX like 25mhz sparc4c? That could be one of the reasons it takes so long

Hee hee.

Mine is a 40MHz... Yup, I know that little lunchbox takes a couple weeks. But that time was doubled with 3.03. Still, I think because of the FFT routines, the Sparcs don't seem to do well. But I guess the consolation is that the SETI dataserver is running on a box with Ultrasparc IIs.

 

[n0cmonkey]

Originally posted by: Poof

Originally posted by: n0cmonkey

Isnt the IPX like 25mhz sparc4c? That could be one of the reasons it takes so long

Hee hee.

Mine is a 40MHz... Yup, I know that little lunchbox takes a couple weeks. But that time was doubled with 3.03. Still, I think because of the FFT routines, the Sparcs don't seem to do well. But I guess the consolation is that the SETI dataserver is running on a box with Ultrasparc IIs.

Thats faster than the processor I had in the SS10.

Sparcs have a history of doing poorly in these things dont they? The routines for rc5 were done in software for the sparc because there was not a hardware instruction or something...

 

[n0cmonkey]

Im going to keep an eye on things but it looks like setistack and setiview will work together.

 

[Assimilator1]

ColinP used to run SETI on various SPARC machines ,I remember him sayingprior to v3.03 (& maybe v3.0) the SPARCS used to be relatively fast at SETI!

Insidious
Why drift off into oblivion with a team whose output eclipses your own and makes you feel like a small insignificant speck ???

No one is an insignificant spec in SETI TA ,even if you're just doing 1WU/day it all counts ,also that is a catch 22 arguement you wally ,when the DF team gets big are you going to leave because of that?
Btw I don't have a problem you promoting DF ,but its not on to diss another project by giving negative comments like makes you feel like a small insignificant speck ???

 

[Crazee]

I have to second Assimilator1 on this. As someone who has run and will run DF again in the future, it is not appealing to me to see recruiting by negative comments towards another project. Please try to keep things positive in regard to the benefits of your selected project, afterall if you can't win people over with the benefits of your project, making negative comments about another one won't help.

That being said, I too like DF and think it is a very worthwhile project that I intend to devote some more resources to when I have the chance.

 

[n0cmonkey]

I dont think the commets are quite as bad as you all are making them out to be. One of the big appeals of eccp109 for me was the ssmaller team. It could have been phrased a little better, but it fit in with the commer-like feel of the rest of the post.