<<
The performance between board manufacturers will not be that different. And even the others are faster than the K7S6A, then it will still only be a little out in front of the KT266A. That just ain't worth it to me. DDR33 + cost of a new motherboard just doesn't justify SiS745's performance right now. >>
Hmmm. I think one thing is that I'm going from the point of view of someone buying new, while you it seems are talking about someoen that allready has 266A am I correct? Let me restate something. Don't get me wrong, I feel that KT266A, and SiS 745 are great chipsets (let's not forget nForce 415-D as well

) and I guess to me, I feel that SiS is at, maybe above VIA's level of compatibility, and stability if it is on the right board. In other words, if I had to choose between 2 otherwise identical boards (lets say Abit KS7 and Abit KR7A), I would take the one with the SiS chipset. But, I do agree that unless board makers use the features (especially Firewire), if someone allready has a 266A, then don't bother.
<<
Yeah ECS have really missed the boat this time but not because of performance which is more than adequate for the market sector its aimed at.
The thing that could have made this board great was to make use of all the chipsets capabilities IMO.
All they needed to do was trace and pop a Firewire port on there and the Digital Video guys would have been queing up for it. 5 or 10$ more with >>
Totally agree RockHard. That really sucked.
<<
Just been sniffing around OCP and they have some benches showing exactly the same kinda thing is likely to happen with the KT333 chipset and the Athlon/XP etc.
Maybe its AMD you guys guys should be dissing and not necessarily the board manufacturers. After all AMD have held onto the 133 (266DDR) FSB a little too long IMO for it to be healthy, yeah? >>
Where? I don't feel like digging. Could you give a link? Btw, you need to type HardOCP, [ H ]ardOCP or you highlite the text
<<
This comment seems to be expressing that running memory asynchronously with the front side bus produces no gains. The Apollo chipsets showed nearly half the benefit of moving the fsb up to the memory speed as well. It is not trivial for a chipset that can implement it properly. 166 asynchronous over 133 should produce 10% real world gain in bandwidth straining applications. >>
When you say Apollo you mean KT133 and KX133? You are correct that running 200fsb Athlon's with PC133 was benefical, but you need to understand how the situation has changed since KT133.
Back in the early Thunderbird days, there was no DDR BUT, the front side bus of the Thunderbird was DDR. The fsb of the T-Bird was 100MHz DDR (200MHz effective) and provided 1.6GB/ps of bandwidth, and when the memory bus was kept in sync with the fsb, the memory bus would be running at PC100 which provides 800MB/ps while the fsb basically was providing double that bandwidth. As a result, KT133's PC133 support while the fsb was running at 100MHz DDR did provide a noticeable increase in performance because there was still bandwidth on the fsb that wasn't being used. Not even PC133 could saturate the 100MHz DDR fsb (PC133 provides 1.064GB/ps of bandy, while the fsb still was providing 1.6GB/ps. Still, 500MB was left to be used). Now, when DDR came upon the scene, PC1600 DDR provided 1.6GB/ps
just like the 200MHz fsb and with 266fsb CPU's, same thing as long as PC2100 DDR was being used. Now, the reason, PC2700 doesn't on SiS 745 and won't help on KT333(A) is because, unlike the situation KT133 came into, KT333(A)/745 comes in with faster memory, but the fsb is allready being saturated by PC2100, and thus the extra bandwidth on the memory bus can't be used.
The thing with KT133 applies to Sis 645 for the Pentium 4 as well. The Pentium 4's fsb is 100MHz QDR (providing 3.2GB/ps of bandwidth), and lets take a synchorous configuration for 645 which isn't very common (PC1600). Again, PC1600 provides 1.6GB/ps, while the fsb still has an extra 1.6GB/ps that can't be used, and this is why 645 gets such a benefit from using PC2100 or even PC2700 is because the fsb still isn't even being maxed out. Do you see what I'm saying now?