Browse Prior Art Database

System and method to intelligently offer application alternatives based on watt calculation

IP.com Disclosure Number: IPCOM000205114D
Publication Date: 2011-Mar-15
Document File: 6 page(s) / 86K

Publishing Venue

The IP.com Prior Art Database

Abstract

System and method to intelligently offer systems which schedule jobs based on software power consumption which takes platform information and application power consumption (total watts used) into consideration when deciding on what server to run a job. The Benefit is lower running costs, by reducing the amount of electricity Software Applications use to execute. Data centres run many jobs across a range of different servers. Many data centres select a server to run a job, based on available system resources and servers which consume the least power (watts). But the actual power consumed by the Software applications itself is not taken into consideration. The Same Software applications could use more or less power (watts), depending on the platform it is executed on. A self learning application could be developed where by a job could be run once in each available server. 1. An application will be given a set number/list of servers to run on. 2. When an application/job runs for the first time with this power saving option on, the same production workload can be simulated to be run on each server. 3. As each application/job completes, the background process updates a data base with the Software application power consumption (watts) costs for each server and also logs the platform these costs are measured on. 4. If there are any hardware or software changes which could change the server performance, then step 2 could be run again to ensure the correct server is selected. 5. You could set-up a priority list of servers for that application. If server 1 was busy then run it on the next best power consumption server keeping platform in mind 6. Once the servers have been evaluated the job scheduler would check the DB for the best server for this application to run on. 7. Providing a run history could also provide benefit for example highlighting possible server/performance issues. If the software Applications power consumption starts to rise then raise an alarm. This could also be applied to laptops and personal PC's. The back ground process stores power consumption information from the applications that are running.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 33% of the total text.

Page 01 of 6

System and method to intelligently offer application alternatives based on watt calculation

When a customer buys a software package there is no consideration to the running costs in terms of power consumption. Today there are many software packages which do more or less the same thing, across many platforms. But the customer does not know the running costs of that software before or even after they buy it for a particular platform.

There are two proposals
1. That all software provides a power consumption (wattage) rating much like any electrical device. This will allow for a tool/website to be developed to compare similar products across all supported platforms. This will provide the customer with a choice to select a similar application which use's less power where they can save on running costs (electricity) over the life time of the software. The same Software may run more efficiently on different platforms. For example comparing the same software running on two different operating systems (OSs) may show that it uses less power on one of them. Thus providing the user with an alternatives platform to run the software on.
2. Create an application/plug in to an existing system which schedules jobs based on software power consumption which takes platform information and application power consumption (total watts used) into consideration when deciding on what server to run a job. The application/plug in would be a self learning in that after running on different servers it would select the server which uses less power based on the total watts used to run that job.

Use Case.

Data centre running jobs across different servers.

    As the job runs to completion statistics are stored about the job, server and total power consumption. Next time round the job is run on a different server storing the same statistics. When the job has run on each possible server the database now holds statistical information about that job on each server including the application power consumption (total watts used). On the next run of the job the database can be checked and the sever which consumed the least power to run the job is where the job would be run.

Prior Art Search

    Has returned methods of calculating the power consumption of software but we did not find anything which combines software power consumption and a tool/website to compare software power consumption of similar products across multiply platforms providing the customer with a alternatives software/platform.

    Also we could not find any prior art on using application consumption (wattage) as a parameter to decide what server a job should run on but again there are some prior art in the area


Page 02 of 6

Method and apparatus for profiling power performance of software applications
US Pat. 7222030 - Filed Feb 6, 2004
- Intel Corporation

Techniques for profiling systems, such as mobile or embedded devices, are provided. The techniques can profile code executing on these systems based on power used b...