Marci
12-18-2002, 04:22 PM
http://forum.folding-community.org/viewtopic.php?t=2762
If you don't have access to that forum, here are the interesting bits....
I do not imagine there is a lot of demand for more than 4 Machine IDs, but I know it would be very useful to some people. Any thoughts on the subject?
I would like this too. We have several Xeon machines with HT enabled which will in the not too distant future have 4 real processors which would mean 8 processors would be available to fold per machine and with only 4 ID's this would leave about 33% of the total CPU power running idle:(
The machine ID# designates the CPU that a client is using. This is used for dual or quad systems that have more than 1 CPU.
As the clients now look in the registy for the user ID# there had to be a way to distingusih between the CPU that the client was using or the AS would send you the same unit to work on thinking that they were the same client. This meant that you would only get credit for one of the units returned because the recieving server would see that that client already turned in that unit.
Thus, if you have a system with more than one client per OS you have to install them in seperat directories and assign them different Machine ID#'s for the different CPU's on that system.
This is not recomended for singel CPU systems as running more than one client on a singe CPU system will slow the return of the units thus hindering the project.
All that has been said is true. What hasn't been said is the fundamental purpose.
The server sends out work to many CPUs and keeps careful track of what's out there and who's got it. Having a unique identifying number for your computer would allow it to keep track of the work it sent you - - provided you only only work on one WU at at time. If you have multiple CPUs within a single machine, you need one WU per CPU, so you need a unique identifier for each CPU, as well.
That's all the useful comments from the thread... figured it was nothing that should be for the eyes of only the beta team....
If you don't have access to that forum, here are the interesting bits....
I do not imagine there is a lot of demand for more than 4 Machine IDs, but I know it would be very useful to some people. Any thoughts on the subject?
I would like this too. We have several Xeon machines with HT enabled which will in the not too distant future have 4 real processors which would mean 8 processors would be available to fold per machine and with only 4 ID's this would leave about 33% of the total CPU power running idle:(
The machine ID# designates the CPU that a client is using. This is used for dual or quad systems that have more than 1 CPU.
As the clients now look in the registy for the user ID# there had to be a way to distingusih between the CPU that the client was using or the AS would send you the same unit to work on thinking that they were the same client. This meant that you would only get credit for one of the units returned because the recieving server would see that that client already turned in that unit.
Thus, if you have a system with more than one client per OS you have to install them in seperat directories and assign them different Machine ID#'s for the different CPU's on that system.
This is not recomended for singel CPU systems as running more than one client on a singe CPU system will slow the return of the units thus hindering the project.
All that has been said is true. What hasn't been said is the fundamental purpose.
The server sends out work to many CPUs and keeps careful track of what's out there and who's got it. Having a unique identifying number for your computer would allow it to keep track of the work it sent you - - provided you only only work on one WU at at time. If you have multiple CPUs within a single machine, you need one WU per CPU, so you need a unique identifier for each CPU, as well.
That's all the useful comments from the thread... figured it was nothing that should be for the eyes of only the beta team....