Specifications and questions
Individual module specifications for the XMS3200LL parts.
- CAS latency: 2.0 clock cycles
- RAS precharge: 2 cycles
- RAS-to-CAS delay: 2 cycles
- RAS active to precharge: 5 cycles for PC2700, 6 cycles for PC3200
- Command rate: 1T (1 cycle)
TWINX Kits
- TWINX512-2700LL: 512 Mbytes, 333 MHz, low latency module pair, kit consists of two matched CMX256A-2700LL DIMMs
- TWINX512-3200LL: 512 Mbytes, 400 MHz, low latency module pair, kit consists of two matched CMX256A-3200LL DIMMs
- TWINX1024-2700LL: 1 Gbyte, 333 MHz, low latency module pair, kit consists of two matched CMX512-2700LL DIMMs
- TWINX1024-3200LL: 1 Gbyte, 400 MHz, low latency module pair, kit consists of two matched CMX512-3200LL DIMMs
The kits are available in both 512MB (2x256MB, as reviewed here) or 1GB (2x 512MB) bundles. They're also available with PC2700 (166FSB, DDR-333) speeds at a lower price. The same principles apply with those modules. They run at a native 2-2-2-5-T1 at 166FSB, perfect if you want to run your shiny new 333FSB AMD XP at default speeds but with super-strict timings.
Nice hologram, eh ?. You can just about see the 0304001 individual numbers on both 256MB XMS3200LL modules, thereby verifying them to work as a team. It appears as if both of the TWINX modules use 5ns Winbond modules pre-tested to guarantee operation at the specified low latencies.
The questions that present themselves are as follows:
Can the modules run successfully at their tight rated speeds without any difficulty ?
Can they do this as a pair, one of the selling points here ?.
Is there any need for matched memory for dual-channel environments ?. Can two different high-speed modules from two different manufacturers run perfectly in tandem ?.
Is the slight price premium attached to matched memory worth it ?
How far will they go individually and as a pair with a little bit of voltage ?.
Let's answer these as we board the benchmark bus.
