Can Intel catch up in process technology with TSMC was a question asked at IFS2024 earlier this week. ‘When you get behind it takes 10 years to catch up,“ replied …

The post Can Intel Catch TSMC? appeared first on Electronics Weekly .

One to note: the UK Bebras Challenge, a STEM computing competition, is now open for registrations for 2024. Thanks to the Raspberry Pi team for highlighting this one.

The post UK Bebras Challenge 2024 opens for entries appeared first on Electronics Weekly .

Chalmers University of Technology in Sweden has revealed its third generation of structural lithium ion battery. “We have created a battery made of carbon fibre composite that is as stiff …

The post Battery can be used as physical structure appeared first on Electronics Weekly .

Google is rebranding TensorFlow Lite to LiteRT (as in “lite runtime”). This lets you deploy ML and AI models on Android, iOS, and embedded devices. Basically, for on-device AI at …

The post Google rebrands TensorFlow Lite to LiteRT appeared first on Electronics Weekly .

TSMC’s August revenue of $7.8 billion was up 33% y-o-y and down 2.4% m-o-m. Revenue for January-August 2024 was $55 billion. Demand for leading edge processes, particularly iPhone chips ahead …

The post TSMC August revenues up 33% appeared first on Electronics Weekly .

The NAND ASP increased by 15% in Q2 and driving total revenue to $16.796 billion – 14.2% up q-o-q, reports TrendForce. All NAND Flash suppliers returned to profitability starting in …

The post Q2 NAND ASP up 15% appeared first on Electronics Weekly .

“There’s a horrible uncertainty about this year which we really don’t know the answers to,“ said Malcolm Penn (pictured) CEO of Future Horizons at IFS 2024 yesterday. Last year started …

The post Horrible Uncertainty appeared first on Electronics Weekly .

Aiming at vehicle traction, Infineon has put a pair of 3,300V 1,000A 1.9 mΩ silicon carbide trench mosfets into its 100 x 140 x 40mm ‘XHP 2’ module housing, calling …

The post SiC half-bridge handles 1.8MW in under 500ns appeared first on Electronics Weekly .

Starting today, Amazon EMR on EC2 offers improved reliability and cluster launch experience for instance fleet clusters through enhanced subnet selection. With this feature, EMR on EC2 reduces cluster launch failures caused due to IP address shortages.

Amazon EMR is a cloud big data platform for data processing, interactive analysis, and machine learning using open-source frameworks such as Apache Spark , Apache Hive , and Presto . Previously, the subnet selection for EMR clusters only considered the available IP addresses for the core instance fleet. Amazon EMR now employs subnet filtering at cluster launch and selects one of the subnets that have adequate available IP addresses to successfully launch all instance fleets. If EMR cannot find a subnet with sufficient IP addresses to launch the whole cluster, it will prioritize the subnet that can at least launch the core and primary instance fleets. In this scenario, EMR will also publish a CloudWatch warning event to notify the user. If none of the configured subnets can be used to provision core and primary fleet, EMR will fail the cluster launch and provide a critical error event. These CloudWatch events enables you to monitor your clusters and take remedial actions as necessary.

Customers will benefit from this feature on all EMR 5.12.1 and later releases when launching EMR instance fleet clusters using allocation strategies. No further action is needed from your end. This capability is available in all AWS Regions , including the AWS GovCloud (US) Regions , where Amazon EMR on EC2 is available. To learn more, please refer to the documentation here .

Amazon CloudWatch Container Insights now auto-discovers the health status of your SageMaker HyperPod nodes running on EKS and visualizes them in curated dashboards to help you monitor your node availability for operational excellence. Using out-of-the-box dashboards, you can identify unhealthy nodes easily and mitigate quickly to achieve efficient training durations.

Container Insights works with SageMaker to collect deep health check test results for HyperPod nodes and displays them in preset dashboards to help you understand the health and performance of your nodes, and identify if they are ready for scheduling. Container Insights assists you in optimizing training durations by classifying failing nodes as “pending reboot” and “pending replacement,” and guiding you on maintaining node health in case automatic node replacement is disabled. If auto-recovery is enabled, you can gain visibility into your node mutations, delays in your training jobs, and understand how your tasks resume from the last check-point.

Getting started with Container Insights is easy. You can onboard either by installing CloudWatch Observability EKS Add-on or the latest CloudWatch agent into your clusters, or upgrading your Helm charts with the latest CloudWatch Agent version. Once configured you can navigate to Container Insights console and view your SageMaker Hyperpod node health status out-of-the-box.

SageMaker HyperPod node health observability is now available in Container Insights for EKS in all commercial regions where SageMaker HyperPod is present. HyperPod node health metrics follow observation based pricing – see Container Insights pricing page for details. For further information, see the Container Insights user guide.