Tyan S2662: Stress Testing

The S2662 had some pretty decent stress testing potential, mostly because it's based on a dual channel chipset (E7205), which is a more complex and difficult chipset to implement (due to signal integrity, among other issues) than the conventional single channel DDR chipsets that dominate today's markets. However, since this BIOS allowed no overclocking whatsoever, our stress tests only consist of memory testing. Here's what we managed to include:

  1. Memory stress testing was conducted by running RAM at 266MHz with two banks full and at 266MHz with four banks full at the most aggressive timings possible.

Memory Stress Test Results:

Running two modules of Corsair XMS memory at dual DDR266 should be very easy for the Tyan S2662. Indeed, it was quite easy, although we were of course unable to adjust any timings since the S2662 BIOS contained no such adjustments:

Stable Dual DDR266 Timings
(2/4 banks populated)

Clock Speed:
133MHz
Timing Mode:
N/A
CAS Latency:
N/A
Bank Interleave:
N/A
Precharge to Active:
N/A
Active to Precharge:
N/A
Active to CMD:
N/A
Command Rate:
N/A

Pretty good timings, eh? No, there obviously aren't any timings we can analyze here, but if you skip a few pages to our stock benchmark testing, you'll see that the Tyan S2662 is able to compete admirably with ASUS and Gigabyte's E7205 solutions, which have been tweaked to the max for performance. At dual DDR266, the S2662 was quite stable, as it was able to complete our entire benchmark suite, which includes Sysmark 2002, Quake3 Arena, Jedi Knight II, Unreal Tournament 2003, SPECviewperf 7.0, Sciencemark, and XMPEG. Prime95 ran for only a few hours, since we were strapped for time in getting this review out the door. Still, all in all, our results give a pretty decent indication that the S2662 can handle dual DDR266, and everyone should expect it to.

In this next scenario we test how well the Tyan S2662 can handle a full load of memory modules:

Stable Dual DDR266 Timings
(4/4 banks populated)

Clock Speed:
133MHz
Timing Mode:
N/A
CAS Latency:
N/A
Bank Interleave:
N/A
Precharge to Active:
N/A
Active to Precharge:
N/A
Active to CMD:
N/A
Command Rate:
N/A

Everything ran smoothly with four DIMMs populated running at 266MHz. We were able to complete a few hours of Prime95 torture testing as well as other general apps.

We should remind you that all the E7205 motherboards we've tested here today (S2662 included) can only operate a certain amount of modules in a specific way. You can always operate this board with one module or with two modules installed, that's not surprising. However, if you want to add a third module to memory bank 3 or 4, you won't be so lucky. E7205 motherboards will simply disable the third module, and operate with just the two modules in banks 1 and 2. Clearly though, you'll be able to operate four DIMMs successfully, so there's nothing to worry about there.

Another issue we wanted to explore was how well Granite Bay would be able to run multiple types of memory modules. Therefore, we tested the most stressful situation possible and installed 4 DIMMs into the S2662. One scenario included four Corsair XMS modules installed, and the other dealt with two Corsair XMS modules (Winbond chips) and two Mushkin modules (Winbond chips). We successfully booted into Windows and played around for a while in both scenarios. All of our usual activities (like running XMPEG movies, data compression, DX8 games, etc.) worked perfectly fine in both situations. It seems as if you'll be able to operate different types of memory modules with the S2662, although we would have to do much more testing to be sure.

Tyan S2662: BIOS and Overclocking Tyan S2662: Tech Support and RMA
Comments Locked

2 Comments

View All Comments

  • hrumsey - Friday, January 7, 2005 - link

    Regarding previous comment:

    And I told this thing to show e-mail address. hrumsey@charter.net if anyone has questions.

    It also removed paragraph indents that would make the above post a bit more readable- apologies.

    And a clarification: The ZCR card could be seen to be flashed only because a jumper change is needed to put them in flash mode. In normal mode, the Thunder K8S Pro S2882 BIOS was squashing the Adaptec 2010S / 2015S BIOS.

    Damn, I hope Google indexes that comment well.

    Speaking of which, for you-know-who:

    Tyan Thunder K8S Pro Adaptec 2010S 2015S ZCR RAID BIOS problem incompatibility bug hang failure download flash PCI-X

    Tyan 2882 K8S Pro Thunder ZCR Adaptec 2015S 2010S RAID bug hang failure problem incompatibility PCI-X flash BIOS download

    Thunder Tyan 2882 K8S Pro ZCR Adaptec RAID 2010S 2015S BIOS incompatibility problem failure hang PCI-X BIOS bug flash download

    wildly incompetent screen-reading technical support monkeys

    beta-testing on customers

    See previous comment
  • hrumsey - Friday, January 7, 2005 - link

    Anandtech's evaluation covers how good Tyan's tech support is in the absence of any real problem for them to deal with. I would suggest that this is not an adequate criterion.
    Our experiences were different.
    The issue of product quality is relevant here, since it makes the quality of technical support more important if the product is poor. My company tried Tyan boards several years ago, and gave up when along with 4 DOAs, 3 quick in-service failures gave a defective rate of almost 50%. I mistakenly thought almost 10 years would be enough for the company to straighten out.
    We ordered 3 Thunder Pro S2882s for a client taking a website inhouse who wanted a 64-bit option- this was before Intel's 64-bit Xeons showed up.
    All of the following happened under time pressure, which isn't unusual, and why better support than Tyan's is necessary:
    One of the three boards was DOA; wouldn't flash any of three Adaptec 2010S ZCR cards; the other two would. Tyan's tech support essentially kept assuming we were doing something wrong and, and at one point asked if we had the current BIOS on the ZCR cards. They must not have any sort of decent database, since the problem had to be explained anew every call. After they admitted the board was bad, they failed to warn us of their shipping deadline for replacing the board (which they will do, and with an E. Coast vendor and them in CA was necessary).
    All the boards failed to see the ZCR cards. First tech said that couldn't be happening, second knew about the problem and said the "E" BIOS fixed it. It didn't. We delivered servers with drives unmirrored.
    Site setup was busy for a while. When I finally had a chance to work on ZCR problem, Tyan could find no record of the problem (none of the emails we exchanged except ones I sent had case #s in the header). I explained everything again, and once again had to assure them again that we'd gotten the obvious stuff right. First tech said he didn't know how it could be happening, and thought I was missing something. Got email next day from supervisor acknowledging there was a problem and saying (again) they had a new BIOS out that would fix the problem. Downloaded, sent tech onsite to install. Didn't work, same result- ZCR card option grayed out in BIOS, system hangs. When I had a chance to go down and work on it personally, once again, no record of case. I went through everything from scratch once more, assuring them that yes, we'd read the FAQs and yes, the system was plugged in, and yes, we had tried every possible combination of their two blasted relevant jumpers, and that in fact there were about eight other germane parameters we had tried which none of them had thought of- and all of this while wasting valuable onsite time. When I finally convinced them that 1) we were competent and 2) it wasn't working, I was told I'd get a call back "shortly" from the responsible engineer. Three hours later, in a darkened factory, at 5:14:55 just as I was leaving, I got a call back from the engineer who actually knew what was going on. He finally admitted we had everything right. He had no solution, but agreed with my suggestion for testing and said he'd check- he lacked authority(!)- to see if management would authorize the replacement board I'd been asking for. And they did, but there shouldn't have been any question.
    Next trip down I replaced the board in one server, picking the server in whichhe Gigabit Ethernet ports had failed- and it still didn't #$%^& work. Tyan said it had been working the day before for them with a 2010S ZCR card, and until today, I didn't know whether they were lying or not. I cussed some and ordered $1200 worth of controllers to replace what Tyan couldn't get right 5 months after the product's release.
    Today I checked and saw that they have a new BIOS for the board available that "Fixes PCI ZCR card hangs system during POST". It's the third BIOS for which they've made that claim, and you know, it really doesn't matter whether they're right this time or not. And if they're not, it doesn't matter whether they're just mistaken or actually lying- theend result is the same.
    We saw five of their high-end server boards. One DOA, one in-service failure, all five with a major design flaw. Eight years is enough time to take care of company-wide failures. Any company that will release a $500 server board with a 40% failure rate, and without first ensuring that everything on it actually works, and who then can't tell for five months whether or not they've fixed the resulting problems, and whose tech support is staffed with folks who can't deal those problems- well, that's a company whose products you want to steer very clear of.

Log in

Don't have an account? Sign up now