Profiling Sustainability of Data Centers

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Profiling Sustainability of Data Centers
# 1  
Old 03-22-2010
Profiling Sustainability of Data Centers

HPL-2010-41 Profiling Sustainability of Data Centers - Gmach, Daniel; Chen, Yuan; Shah, Amip; Rolia, Jerry; Bash, Cullen; Christian, Tom; Sharma, Ratnesh
Keyword(s): Data Center, Energy Profiling, Resource Management
Abstract: Today's data centers consume vast amounts of energy, leading to high operational costs, excessive water consumption, and significant greenhouse gas emissions. With the approach of micro grids, an opportunity exists to reduce the environmental impact and cost of power in data centers. To realize this ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. AIX

C profiling tool for AIX

Hello everybody, Please let me know if there are any free C profiling tool for AIX environment Thanks in advance (0 Replies)
Discussion started by: SteAlma
0 Replies

2. Programming

Profiling results and SMP

The SCO OSR 5.7 system was migrated from older HP DL360 to new DL380 G7. The SMP feature was not activated on older box, it is activated now on this 4 core Xeon. A s/w we maintain has been copied without any change over to the new box. I noticed that the application profiling does not show any... (4 Replies)
Discussion started by: migurus
4 Replies

3. UNIX for Advanced & Expert Users

Kernel Profiling

I compiled my device driver with the profiling option -p but while linking I am getting undefined reference to _mcount. LD /vobs/femto_drivers/DspBiosLink/dsplinkk/src/dsplinkk.o Building modules, stage 2. MODPOST *** Warning: "_mcount" undefined! Architechture: ppc32 From... (0 Replies)
Discussion started by: Ashok V
0 Replies

4. Virtualization and Cloud Computing

Event Cloud Computing - IBM Turning Data Centers Into ?Computing Cloud?

Tim Bass Thu, 15 Nov 2007 23:55:07 +0000 *I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question
MPI_Pcontrol(3OpenMPI)													    MPI_Pcontrol(3OpenMPI)

NAME
MPI_Pcontrol - Controls profiling. SYNTAX
C Syntax #include <mpi.h> int MPI_Pcontrol(const int level, ... ) Fortran Syntax INCLUDE 'mpif.h' MPI_PCONTROL(LEVEL) INTEGER LEVEL, ... C++ Syntax #include <mpi.h> void Pcontrol(const int level, ...) INPUT PARAMETER
level Profiling level. DESCRIPTION
MPI libraries themselves make no use of this routine; they simply return immediately to the user code. However the presence of calls to this routine allows a profiling package to be explicitly called by the user. Since MPI has no control of the implementation of the profiling code, we are unable to specify precisely the semantics that will be pro- vided by calls to MPI_Pcontrol. This vagueness extends to the number of arguments to the function, and their datatypes. However to provide some level of portability of user codes to different profiling libraries, we request the following meanings for certain values of level: o level==0 Profiling is disabled. o level==1 Profiling is enabled at a normal default level of detail. o level==2 Profile buffers are flushed. (This may be a no-op in some profilers). o All other values of level have profile library-defined effects and additional arguments. We also request that the default state after MPI_Init has been called is for profiling to be enabled at the normal default level (i.e., as if MPI_Pcontrol had just been called with the argument 1). This allows users to link with a profiling library and obtain profile output without having to modify their source code at all. The provision of MPI_Pcontrol as a no-op in the standard MPI library allows users to modify their source code to obtain more detailed pro- filing information, but still be able to link exactly the same code against the standard MPI library. NOTES
This routine provides a common interface for profiling control. The interpretation of level and any other arguments is left to the profil- ing library. This function does not return an error value. Consequently, the result of calling it before MPI_Init or after MPI_Finalize is undefined. Open MPI 1.2 September 2006 MPI_Pcontrol(3OpenMPI)