which linux seti is quicker?

[cakin]

running dual p2-333's, planning on running seti under wine,
which is better: i686-pc-linux-gnu-gnulibc2.1 or i686-pc-linux-gnulibc1-static

 

[Rendus]

Better would be the non-static one, but not because it'll be much faster, but rather it's going to use less RAM.

The static binaries don't rely on any external libraries, and doesn't share routines with other programs that would use the same libraries. Meaning it has a larger memory footprint. The non-static ones will use external libraries, which are only loaded into memory when needed. Since the major library in use would be glibc, it comes at a substantially smaller memory footprint than the static binary, as glibc is usually in memory to begin with.

But you plan on running it under Wine. If that's the case, you'll need the NT binaries, as Wine will "emulate" Windows, allowing the NT version to run, which is faster than the Linux version to begin with, and Wine runs the NT version faster than NT runs the NT version.

 

[Electrode]

that reminds me, I'm in the process of switching my dual p3 733 to linux, and I already have one windows cli client running under wine, but how would I run 2? these are the problems I'm having:

1. S@H seems to want to store the data in my home directory, and that wouldn't go when running 2 clients.
2. How would I make each client only use 1 CPU? In windows, I'd start the client then go to task manager and set the process affinity for each to a single CPU.

 

[Sukhoi]

You guys will probably want to talk to Poof about running multiple instances in WINE, I think she may have experience doing that.

Could you start up the Linux client, and then start WINE and run another client in there?

 

[Electrode]

well, I just did the first thing you should do but the last thing you usually do: RTFM

There's a switch for all clients (except maybe win/mac gui) that tells it to use only one cpu. Just run it like this:

wine -- /path/to/client/seti -proxy address.of.your.setiqueue -cpu 0

That would work if you wanted it to run on your first CPU. replace 0 with 1 to use your second, and so on.

Also, I think seti will use whatever your working directory is. if you cd to /home/you/seti2 and invoke seti from there, the data will be stored there.

Just guessing tho. I'll have to try it.