Skip to Content

Let us now have a look at the emerging power-saving technology trends. How to use them best is a challenge primarily for the technology developers at SAP. Software must support the available power saving techniques at both the hardware and the software level:

  • On the hardware level CPUs, the main power consumers, are getting more and more power-aware.
  • On the software level, SAP software must support and actively integrate the new power management functionalities of the CPUs and the operating systems.

One direction that in-memory computing is going is to achieve unified real-time analytical capabilities by combining OLTP (Online transaction procession) and OLAP (Online analytical processing) in a single in-memory database.

In the related article we discuss the following topics with regards to sustainable programming in more detail:

  • Accounting for energy-saving technologies on hardware level
  • Accounting for energy-saving technologies on software level
  • Main Memory Computing

Please let us know what you think about how software should support the available power saving techniques at both the hardware and the software level.

How important is this topic within your company?

Your insights will help us immensely.

Please give us feedback via this blog or via mail:


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Thank you very much for the insights on Power-Saving Technology.

    My very personal opinion is slightly different:

    Although Power-Saving is extremely important for our all survival, the reality does not follow.

    More and more companies believe what some (SAP) technicians tell them:

    You need more servers:

    One for central ERP, next one for BI, another one for APO.

    No, for APO you need one for Global ATP, one more for Forecast & Replenishment, a third one for transport management.

    Not to forget a server for warehouse management, a server for Track and Trace … and at least for security reasons an own server for financials.

    Sorry I forgot the PI system that is a must-middleware connecting all the servers – nothing could be done if data is not synchronized permanantly between all the servers.

    And if you want to talk to your customer, you need a system for Customer-Interaction…

    At least it creates a lot of jobs for people doing the administration of all those systems and interfaces.

    And then still you have hundreds or thousands of users that keep one or two PCs running overnight because it takes so much time to shut down and power-up again.

    Conclusion: Your blog series shows up an enormous potential, we can still hope that decision-makers will get aware of it.


  2. Eric Poellinger
    I have been seeing the trend of lower frequency CPUs and the impact on Single Threaded performance for many years.  It exposes an architectural flaw I see in MANY deployments for custom-built solutions : you upgrade your hardware and things get a little slower because you didn’t parallelize from the beginning.

    Seems to me there is a TON of unused CPU power in many environments.  Maybe the concept of a dialog vs batch split comes into play : i.e. you accept some CPU ‘waste’ on the dialog side because users don’t want to wait — but for batch processing, you can throttle up/down without too much concern (i.e. if a batch job has to wait 30-60 seconds for CPUs do become “un-parked” will anyone really know).  I think ABAP Netweaver has some elements of this today with dynamically increasing work processes, but I don’t know much about the ability to communicate with the HW directly (vs the HW deciding when its time to park completely on its own).

    I’m very happy to see SAP is aware of this, as well as the broader ability to reduce power consumption.  My experience is that SAP takes a longer than most want to figure something out, but when they do it is done really well. 


Leave a Reply