AWS

Echo addresses the bandwidth bottleneck in tensor parallelism by transmitting 4-bit values during all-reduce operations, cutting communication costs by nearly 4x compared to 16-bit. It prevents accuracy degradation by performing summations in high precision and quantizing each value at most twice per call. This approach controls accumulated rounding errors that typically emerge when reducing precision across dependent matrix multiplications.

• Reduces tensor parallel all-reduce bandwidth usage by ~4x via 4-bit transmission.
• Maintains model quality by summing in high precision while transmitting low precision.
• Limits quantization to at most two operations per value per all-reduce call.
• Applies error compensation to mitigate accumulation of rounding errors across layers.

Amazon RDS Custom for SQL Server exposes OS-level access, revealing internal volumes like W: that appear as raw, uninitialized disks. The architecture maps C:, D:, and W: drives to specific Amazon EBS volumes, requiring careful handling to avoid data loss. This guidance details safe disk operations and verification checks to protect your database infrastructure.

• W: drive appears as raw, uninitialized disk due to OS-level access in RDS Custom.
• C:, D:, and W: drives map directly to underlying Amazon EBS volumes.
• Follow specific safe disk operations to prevent accidental data destruction.
• Use verification checks to ensure storage integrity before making changes.

Fleet impact: For RDS Custom for SQL Server, do not initialize or format the W: drive, as it is critical for internal database files. Verify EBS volume mappings before any storage-level maintenance to avoid orphaning data or breaking the replication topology.

A new study measures the energy consumption of 86 open-weight LLM checkpoints across seven benchmarks and six hardware platforms. The results show significant variance in efficiency, with many configurations using up to 4.8 times more energy than necessary to achieve comparable benchmark scores. Enabling reasoning modes increases energy usage by an average of 3.7 times, though the performance benefit varies by model family.

• Benchmark scores do not reflect energy costs, leading to inefficient model deployments.
• Many model configurations are far from the Pareto frontier, wasting up to 27x energy.
• Reasoning modes boost capability but triple energy consumption on average.
• Efficiency gains depend heavily on specific model families and hardware choices.
• Practitioners should audit energy usage alongside accuracy for cost-effective inference.

Amazon ECS introduces LiveTaskCount, a new metric tracking tasks across all active states including activation and deactivation phases. This replaces the previously billed RunningTaskCount metric, which is now provided at no additional cost. The updated metric supports more accurate autoscaling and capacity planning by capturing tasks during connection draining.

• LiveTaskCount covers ACTIVATING, RUNNING, and DEACTIVATING states
• RunningTaskCount charges are removed from CloudWatch Container Insights
• Captures tasks during scale-in connection draining for accuracy
• Improves reliability for autoscaling policy decisions