Why I won't upgrade to the latest client when it's released.

[Jator]

With the 8012 client issue, I've decided to stay with the 8010 & 8011 on all of my machines for the time being even after the new client is released (looks like it will be 8014). I don't think they can optimize the client any faster than they already have for the Athlons and Pentiums that dominate our herds, and I would rather not have to downgrade over 30 machines again. So I think from now on I will always stay one or two versions behind the current client to ensure I don't get stuck with a bad client again.

Not trying to say anything bad about DNet or their clients. I'm just going to be a little more conservative and not upgrade simply yo have the latest clients.

Jay

P.S. Now, if the new client turns out to be a lot faster, well exceptions can always be made.

 

[networkman]

Don't worry Jator, I'm taking a similar approach.

Actually, this is the same tactic that's used by many Network Administrators.. unless you're having problems, don't jump to install the latest OS patch, regardless of what OS it is.

 

[Slahr Dzhe]

Cut and pasted from my client on this machine:

dnetc v2.8005-455-CTR-00011619 for Win32

As you can see, I have not upgraded in a very long time as this one works fine. I have been operating computers for too long to know that new does not equal better. Unless someone can say that a newer client will give me a significant boost in performance on this old P3@560, I will leave it as is.

SD

 

[BurntKooshie]

Snip...

<< I don't think they can optimize the client any faster than they already have for the Athlons... >>

Snip...

I beg to differ.

 

[ViRGE]

There's only 1 problem with that BK, in all that time, they haven't actually gotten the Athlon past 3.4.:|

 

[phatstyl]

Hey, hes looking for a team to join =)

 

[Jator]

BK,

I stand corrected. I have one Athlon machine, once the new optimixed core come out, I'll look at putting it on my Athlon.

Jay

 

[Gorgonzola]

im still using the first client i ever downloaded. but then again, i've only been cracking for maybe 6 months so it doesn't matter

 

[Eug]

Moose doesn't want us using the 8011 client either. In fact, it never was anything but a beta. He didn't state why, and he didn't even say the work with be disallowed, but he said switch to 8010. So, a few of my Intels are running 10% slower than they should be (using 8010) in OGR. When 8014 comes out, I'll upgrade to that. But truth be known, I've got 8011 running on a few, simply because I've been too lazy to downgrade them.

 

[Dutchman2000]

I'll stick with the fastest client on all machines I have direct acces to (like my own workstation). The &quot;networked&quot; computers are staying @ 8010 for a long long time, downgrading 50 clients by hand was a menace .

 

[Netopia]

I too won't upgrade until I know it's truly stable... at least for the majority of my machines. For the few (about 5 or 6) Gig+ Tbirds, I would happily try out a client that would give 10-15% increase... but only because these machines are easily accessed and I could revert if necessary.

I think that the latest fiasco with the client has left some of us that have larger herds with a bad taste in our mouths. I still love the contest and the Team... but I've learned my lesson about quickly upgrading.

Joe

 

[RaySun2Be]

How many of us don't upgrade to the newest MS OS (except on test/non-critical boxes) until at least service pack 1 or 2 is out?

I got burnt recently by upgrading my ATI Rage vid card with an ATI beta driver for Win2K. What a horrible experience that was. :Q

The only fix was to swipe my son's MX card and use it.

 

[jatwell]

Oh yeah:



<< Version 2.7112.444-CTR-99072212 >>



Heh, that's still running on my Dual Pentium Ghz machine that was once dual 300a's. Don't see much reason to upgrade w/o a performance increase. Works fine

Now all my Athlons are running 8010 clients and get an average of 3.5Mkeys/sec when not used.

 

[IsOs]

Since I only participate in RC5 with DNET, I haven't seen a need to upgrade my clients (v2.7105.432 for Win32). It works without a problem even with DVD playback or 2 DOS SETI clients running concurrent with this client.

 

[SpaceWalker]

Im with jatwell...

This is mine...

RC5DES v2.7112-444-dev-GTR-99061504 client for Win32 (under Windows NT 5.0)

I like the dual proccess graph....

It only runs on my dually at home......

the rest are running the 8010...

MOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOooooooooooooooooooooooooooooo...........

 

[Slacker]

RC5DES v2.7106.436 GUI Client for Win32 (under Windows 4.10) started. my first and only, I hate the CLI's

 

[ViRGE]

Once a 8112 client goes final, there'll be a GUI for you to play with Slacker.

 

[imported_Thunder]

Jator,

If all you're doing is RC5 on Intel P6 cores, then I'd tend to agree... They appear to have milked all the performance they can out of that combination.

However, we all clearly saw MAJOR improvements in OGR performance on Intel's with the .8012 version. Also, the jump in OGR from .8009 to .8010 on Athlons was big, so it's likely there's still a bit more performance to come.

Still, I'm totally in agreement with you as far as changing my more &quot;remote&quot; machines... I'm not going to upgrade unless there's a CLEAR performance gain. The only thing that scares the willies outta me is that I did that with the .8012 clients. I held off on them until others convinced me that I'd see a good OGR boost on my Intels... and still, after a matter of months, we found out there was a fault in them! How long do we wait to upgrade even when there is a clear gain to be had? Hmmmmm?

-Brian