as the title says... that client&manager will have some basic features like return_results_immediately...

Note:
It'll be a stock client without any optimizations turned on and be missing some featues like cpu affinity, double_num_cpus, reset_debs etc etc etc...
will be available to the Team SETI.USA only ... Sorry

you can decide here:
POLL

POLL RESULTS S@H

POLL RESULTS E@H

---

as the title says... that client&manager will have some basic features like return_results_immediately...

Note:
It'll be a stock client without any optimizations turned on and be missing some featues like cpu affinity, double_num_cpus, reset_debs etc etc etc...
will be available to the Team SETI.USA only ... Sorry

you can decide here:
POLL

POLL RESULTS S@H

POLL RESULTS E@H

so we'll be voting on something we cannot use ?

It would be nice to have for those that want to use it, though you should also build in a -report_as switch so it cann report itself to the servers as a x86 client. Else people will have to edit files to get it to run on Rosetta@home, we have no 64bit client for Windows or linux.


P.S. How can you restrict an open source client ?

You may want to target the project with 64bit apps, like SIMAP.

---

Team mauisun.org

I wonder what happens if the project admins simply release the 32bit win client under a different filename and tell the scheduler that that one is for 64 bits?

I think I am right that 32bit apps run on 64bit Win systems? If so that would solve the problem of people with 64 bit Boinc clients getting left out completely.

Perhaps it would be worth experimenting on Ralph?

It would, of course, not run quite as fast as a true 64 bit app, but I have seen an explanation elsewhere that because of the way Rosetta works it is expected to benefit much less from the longer precision than most other BOINC projects.

River~~

---

I wonder what happens if the project admins simply release the 32bit win client under a different filename and tell the scheduler that that one is for 64 bits?

I think I am right that 32bit apps run on 64bit Win systems? If so that would solve the problem of people with 64 bit Boinc clients getting left out completely.

Perhaps it would be worth experimenting on Ralph?

It would, of course, not run quite as fast as a true 64 bit app, but I have seen an explanation elsewhere that because of the way Rosetta works it is expected to benefit much less from the longer precision than most other BOINC projects.

River~~

I think it's negligable increase/decrease for the current amount of clients that would actually use it. That is without a large rewrite of the whole of the Rosetta code. Teh simple re-compile gains little (so says the members looking into it). A complete re-write would be of little benefit unless there was a major usage of 64bits clients, which there are not since very few people use 64bit OS's. It may change with Vista, but who knows. that and the extra expense (time and support) of keeping both branches of 64bit and 32bit up to date.

AFAIK they can just rename the 32bit clients and they work, other projects do that.

---

Team mauisun.org

AFAIK they can just rename the 32bit clients and they work, other projects do that.

I think this would be a wise move for an easy gain of CPU power - greenman on my team had real problems getting Rosetta running using a 64 bit client. I think he gave up in the end. Boinc should just download the 32bit Rosetta app automatically, and if renaming a copy of the file makes that work then thats a quick and easy solution.

Installing the 32bit BOINC client isn't always an option if people are running other 64bit projects too.

Devs - can this be done? If so I can probably get one cruncher to test it asap.

---

I don't see why the BOINC client needs to be 64-bit to work with a 64-bit project - it just RUNS the project executable, it doesn't actually perform any operations on the project executable that requires it to be the same bitness...

You can start a 64-bit application from a 32-bit application in both Linux and Windows, so that's not a limitation. What you can't do is include shared libraries that are different bitness - but that's not a problem for BOINC or Rosetta, as both are static-linked, so don't use shared libraries of the host-system.

However, I believe there are systems out there where the Linux-kernel is built so that it doesn't support 32-bit compatibility mode - why anyone want's to have this restriction I don't know.

It works perfectly fine to install a 32-bit BOINC client on a 64-bit SuSE Linux, and when I did this, it found the correct 32-bit Rosetta (and Seti and Einstein) to work with it.

--
Mats

---