This app has been available for about 7 weeks now. Any ideas when it will become the default Windows app for SSE machines? Surely enough WUs must have been crunched by this now to know whether it is a good version or not?
Ideally the next Windows app would be like the current Linus stock app: a bundle of two apps (one for SSE supporting PCs and one for older hosts) plus a CPU feature detection exe that switches between the two apps. This would probably have to be beta-tested first as well.
The only downside to bundling two apps together is the enormous initial download that entails, which hammers dial-up users pretty badly. That wasn't as big an impact with the Linux app, since it has a much lower share of the total systems out there, but it's a real concern with Windows. It's too bad that the scheduler couldn't have the intelligence to determine which app to send based on the info in the database for the host, but that would likely require a minimum BOINC CC version. So, no easy solutions. I'm sure that whatever is come up with will be the best solution possible.
It's too bad that the scheduler couldn't have the intelligence to determine which app to send based on the info in the database for the host, but that would likely require a minimum BOINC CC version.
I believe that functionality is already there server-side, but as you say, perhaps it requires a fairly new client. (Does the client report it's version to the server? Does E@H know what proportion of hosts are on what client versions?)
An alternative would be to take the SIMAP option: make the SSE app the default, and the non-SSE app available for manual install by power users. My guess is that most of the older CPUs attached here have geek (power user) owners.
I'm sure E@H is missing out on plenty of TFlops at the moment because of this - isn't 4.36 about 30% faster than the current stock app?
I believe that functionality is already there server-side, but as you say, perhaps it requires a fairly new client. (Does the client report it's version to the server? Does E@H know what proportion of hosts are on what client versions?)
Client-side you'll need atleast v6.1.14, since v6.1.13 apparently causes problems with older scheduling-servers, so until there's a stable v6-client released, going this way will have very little effect. Still, already now enabling multiple applications server-side would be an idea, to make sure to iron-out any possible bugs, and immediately benefit as users upgrades to v6.
Client reports it's version to server, and can refuse to talk to outdated clients. Not sure if project automatically gets a list of which particular client sub-version has finished each task, or if it's only going by application-version/platform-combination. But, in any case, the info can be collected from the scheduling-server-logs, similar as SETI@home is doing. A quick look reveals, that of last roughly 10k scheduling-connections, 1.86% of clients runs v6, but only 0.31% runs v6.1.14 or later...
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
But, in any case, the info can be collected from the scheduling-server-logs, similar as SETI@home is doing. A quick look reveals, that of last roughly 10k scheduling-connections, 1.86% of clients runs v6, but only 0.31% runs v6.1.14 or later...
Interesting. Do they have a similar page that shows CPU capabilities? The SSE / non-SSE split would be intersting to see...
Interesting. Do they have a similar page that shows CPU capabilities? The SSE / non-SSE split would be intersting to see...
No, but it should be possible to get a good idea by looking either in various projects stats-dumps, or to look on various stats-sites "host cpu breakdown". Since AFAIK all Intel p3 and later includes SSE, and similarly all Amd Athlon and later, look for pentiums, p2, k6 and cyrix...
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
Interesting. Do they have a similar page that shows CPU capabilities? The SSE / non-SSE split would be intersting to see...
No, but it should be possible to get a good idea by looking either in various projects stats-dumps, or to look on various stats-sites "host cpu breakdown". Since AFAIK all Intel p3 and later includes SSE, and similarly all Amd Athlon and later, look for pentiums, p2, k6 and cyrix...
AMD introduced SSE with the Athlon XP iirc, the "plain" Athlon did not support SSE to a useful extend.
I had successfully run this previously on BOINC version 5.10.45. However the newer BOINC version 6.1.16 is set up differently, and I cannot figure out what file to extract the EAH app. 4.36 into to get it to function.
RE: This app has been
)
Ideally the next Windows app would be like the current Linus stock app: a bundle of two apps (one for SSE supporting PCs and one for older hosts) plus a CPU feature detection exe that switches between the two apps. This would probably have to be beta-tested first as well.
CU
Bikeman
The only downside to bundling
)
The only downside to bundling two apps together is the enormous initial download that entails, which hammers dial-up users pretty badly. That wasn't as big an impact with the Linux app, since it has a much lower share of the total systems out there, but it's a real concern with Windows. It's too bad that the scheduler couldn't have the intelligence to determine which app to send based on the info in the database for the host, but that would likely require a minimum BOINC CC version. So, no easy solutions. I'm sure that whatever is come up with will be the best solution possible.
RE: It's too bad that the
)
I believe that functionality is already there server-side, but as you say, perhaps it requires a fairly new client. (Does the client report it's version to the server? Does E@H know what proportion of hosts are on what client versions?)
An alternative would be to take the SIMAP option: make the SSE app the default, and the non-SSE app available for manual install by power users. My guess is that most of the older CPUs attached here have geek (power user) owners.
I'm sure E@H is missing out on plenty of TFlops at the moment because of this - isn't 4.36 about 30% faster than the current stock app?
RE: I believe that
)
Client-side you'll need atleast v6.1.14, since v6.1.13 apparently causes problems with older scheduling-servers, so until there's a stable v6-client released, going this way will have very little effect. Still, already now enabling multiple applications server-side would be an idea, to make sure to iron-out any possible bugs, and immediately benefit as users upgrades to v6.
Client reports it's version to server, and can refuse to talk to outdated clients. Not sure if project automatically gets a list of which particular client sub-version has finished each task, or if it's only going by application-version/platform-combination. But, in any case, the info can be collected from the scheduling-server-logs, similar as SETI@home is doing. A quick look reveals, that of last roughly 10k scheduling-connections, 1.86% of clients runs v6, but only 0.31% runs v6.1.14 or later...
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
RE: But, in any case, the
)
Interesting. Do they have a similar page that shows CPU capabilities? The SSE / non-SSE split would be intersting to see...
RE: Interesting. Do they
)
No, but it should be possible to get a good idea by looking either in various projects stats-dumps, or to look on various stats-sites "host cpu breakdown". Since AFAIK all Intel p3 and later includes SSE, and similarly all Amd Athlon and later, look for pentiums, p2, k6 and cyrix...
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
RE: RE: Interesting. Do
)
AMD introduced SSE with the Athlon XP iirc, the "plain" Athlon did not support SSE to a useful extend.
CU
Bikeman
Pardon my ignorance, but
)
Pardon my ignorance, but where does one extract this app to if one is using BOINC 6.1.16?
Thanks!
RE: Pardon my ignorance,
)
Here.
RE: RE: Pardon my
)
I had successfully run this previously on BOINC version 5.10.45. However the newer BOINC version 6.1.16 is set up differently, and I cannot figure out what file to extract the EAH app. 4.36 into to get it to function.
Thanks.