MENU
CLOSE
The biggest challenge in cloud computing is delivering the performance needed to handle increasing workloads while minimizing power consumption. Today, data centers consume about 2% of electricity worldwide, and this is increasing dramatically. Networking and server chips remain the primary factor in determining data center performance, power consumption, and cost. Although designers leverage new process nodes, multi-die designs, and new architectures, immense leaps in performance keep driving chip-, system-, and datacenter-power increases.
Data center processors face unique power challenges given their various workloads. At one moment, these chips may be at 10% utilization and suddenly ramp to 50% because of a workload swing. These rapid shifts induce localized and chip-wide voltage droops and simultaneous switching effects, creating ripples across a power network. To prevent timing glitches, designers may margin their voltage budget. However, this can quadratically increase power.
One way to reclaim power efficiency while improving performance is to address the droop issues through adaptive clocking, which scales frequency during voltage fluctuations. The technique requires a highly responsive programmable clocking solution and a droop detection mechanism. The latter may be optional if architects have deterministic workloads that can be managed with prior knowledge, which is rare for merchant silicon providers. In either situation, design teams can reclaim voltage margin, reducing system power while maintaining or increasing system performance through adaptive clocking.
The Aeonic™ platform resolves these issues by providing application-optimized digital components that intelligently orchestrate timing across an SoC. Aeonic enables power-efficient, high-performance solutions for cloud computing.
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. |