MENU
CLOSE
AI and ML workloads are growing in popularity across many industries, leading to great variability in operation types and composition. In February 2021, Microsoft announced its 17 billion parameter language model T-NLG. Less than one year later, Google shattered that record with its 1.6 trillion parameter model Switch-C, almost a 100x increase in model size.
Models (language and vision) continue to grow in size and complexity at an exponential rate. The uncertainty and rapid model growth is driving AI silicon designers to increase performance at unprecedented rates, which has power and time-to-market implications.
While specialized in handling a narrow set of computational operations, AI/ML chips face similar power challenges as CPUs and GPUs. Varying customer workloads create unpredictable voltage droops that can induce timing glitches. As designers build larger synchronous regions, simultaneous switching noise creates larger ripples in the power network. And the rate of compute growth is expanding top-level clocking power consumption. Each of these power-related issues directly impacts BOM costs, system power budgets, and total cost of ownership in terms of power, cooling, and deployed density.
The Movellus Aeonic™ product portfolio provides an application-optimized clocking solution for AI silicon platforms that addresses lost performance due to voltage droops and enables fine-grain performance tuning for large reconfigurable architectures. Aeonic Generate can glitchlessly hop frequencies during a voltage droop to maintain reliable performance and is small enough to be distributed across the SoC for localized clocking and run-time frequency tuning. With a feature-rich, synthesizable platform, architects can use Aeonic to handle dynamic and ever-changing workloads efficiently.
Stay Connected
Stay Connected
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
__hssc | session | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hstc | session | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_F75FB76KBW | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_60322432_1 | 1 minute | Set by Google to distinguish users. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
hubspotutk | session | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |