Sponsored Content
Full Discussion: LPAR CPU capacity planning
Operating Systems AIX LPAR CPU capacity planning Post 302806745 by MichaelFelt on Monday 13th of May 2013 02:40:07 PM
Old 05-13-2013
I do not think this is going to give you a statistic you really want, but I may be mistaken - as it all depends on what you are trying to "relate" to/with each other.

The physc ($PC) value is already "relative" in the sense that you are computing it (I think) because it is an expression of the processing milliseconds used for the time period (9.1 means 91 msec per 10 msec - which is the PHYP real-time scheduling window - entitlement is guaranteed processing - if requested -, in real terms: (EC * 10) msec per 10 msec.

So if I use 91 msec - that might be 10 processors (9 running non-stop for 10msec, and one (the tenth) running only 1msec, or it could be 91 processors all running only 1 msec.

Looking at user/sys time and comparing them to physc could make sense on Power6 and earlier - where one thread running user+sys = 100 could equal physc = 1.0, but on POWER7 a single thread is considered to only be 0.66 of 1.0 while the other three threads (logical cpu 1,2,3 = even though idle is 100% are considered to be "using" .11 physc each - because there are additional processing components on a Power7 that, by definition, are not being used. In other words, it is impossible for a single thread to fully utilize a POWER7 processor potential.

In short, I think the statistic to use is just physc. You could perhaps give it a weight by multiplying it by lbusy% - but this depends on what you are trying to make "standardized".

Hope this helps (i.e. is understandable)!

Michael
 

7 More Discussions You Might Find Interesting

1. Solaris

Planning for DR, I have to collect information

Dear All, We are going for Disaster Recovery project, the vendor asked for more details about how much is the daily data changes only. using sar / iostat can any one help me to collect this ?! Note: only I need the changed data size not the daily increasing data. this is to know how much... (1 Reply)
Discussion started by: adel8483
1 Replies

2. What is on Your Mind?

Planning to be certified , your advice?

Hi, I got 2 courses Intermediate and advanced Solaris 10 Administration before 1 month. I was studying the material of the 1st course I will finish it soon. I want to get the Exam. What is your advice? Which is the best Exam Quastion ( Testking or ,,,,,,,, Etc) .... Regards (1 Reply)
Discussion started by: adel8483
1 Replies

3. AIX

capacity planning on aix

Hi All, What do you usually use for capacity planning on AIX? Any idea will do? Thanks in advance, itik (1 Reply)
Discussion started by: itik
1 Replies

4. Solaris

tools for capacity planning

Hi All, What do you usually use for capacity planning tool on solaris 8 or later? Thanks in advance. (2 Replies)
Discussion started by: itik
2 Replies

5. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

6. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

7. AIX

FS capacity

can anyone tell me how to reduce Fs capacity by using echo zero. (3 Replies)
Discussion started by: nkchand
3 Replies
QTimer(3qt)															       QTimer(3qt)

NAME
QTimer - Timer signals and single-shot timers SYNOPSIS
#include <qtimer.h> Inherits QObject. Public Members QTimer ( QObject * parent = 0, const char * name = 0 ) ~QTimer () bool isActive () const int start ( int msec, bool sshot = FALSE ) void changeInterval ( int msec ) void stop () int timerId () const Signals void timeout () Static Public Members void singleShot ( int msec, QObject * receiver, const char * member ) DESCRIPTION
The QTimer class provides timer signals and single-shot timers. It uses timer events internally to provide a more versatile timer. QTimer is very easy to use: create a QTimer, call start() to start it and connect its timeout() to the appropriate slots. When the time is up it will emit the timeout() signal. Note that a QTimer object is destroyed automatically when its parent object is destroyed. Example: QTimer *timer = new QTimer( myObject ); connect( timer, SIGNAL(timeout()), myObject, SLOT(timerDone()) ); timer->start( 2000, TRUE ); // 2 seconds single-shot timer You can also use the static singleShot() function to create a single shot timer. As a special case, a QTimer with timeout 0 times out as soon as all the events in the window system's event queue have been processed. This can be used to do heavy work while providing a snappy user interface: QTimer *t = new QTimer( myObject ); connect( t, SIGNAL(timeout()), SLOT(processOneThing()) ); t->start( 0, FALSE ); myObject->processOneThing() will be called repeatedly and should return quickly (typically after processing one data item) so that Qt can deliver events to widgets and stop the timer as soon as it has done all its work. This is the traditional way of implementing heavy work in GUI applications; multi-threading is now becoming available on more and more platforms, and we expect that null events will eventually be replaced by threading. Note that QTimer's accuracy depends on the underlying operating system and hardware. Most platforms support an accuracy of 20ms; some provide more. If Qt is unable to deliver the requested number of timer clicks, it will silently discard some. An alternative to using QTimer is to call QObject::startTimer() for your object and reimplement the QObject::timerEvent() event handler in your class (which must, of course, inherit QObject). The disadvantage is that timerEvent() does not support such high-level features as single-shot timers or signals. Some operating systems limit the number of timers that may be used; Qt tries to work around these limitations. See also Event Classes and Time and Date. MEMBER FUNCTION DOCUMENTATION
QTimer::QTimer ( QObject * parent = 0, const char * name = 0 ) Constructs a timer called name, with the parent parent. Note that the parent object's destructor will destroy this timer object. QTimer::~QTimer () Destroys the timer. void QTimer::changeInterval ( int msec ) Changes the timeout interval to msec milliseconds. If the timer signal is pending, it will be stopped and restarted; otherwise it will be started. See also start() and isActive(). bool QTimer::isActive () const Returns TRUE if the timer is running (pending); otherwise returns FALSE. Example: t11/cannon.cpp. void QTimer::singleShot ( int msec, QObject * receiver, const char * member ) [static] This static function calls a slot after a given time interval. It is very convenient to use this function because you do not need to bother with a timerEvent or to create a local QTimer object. Example: #include <qapplication.h> #include <qtimer.h> int main( int argc, char **argv ) { QApplication a( argc, argv ); QTimer::singleShot( 10*60*1000, &a, SLOT(quit()) ); ... // create and show your widgets return a.exec(); } This sample program automatically terminates after 10 minutes (i.e. 600000 milliseconds). The receiver is the receiving object and the member is the slot. The time interval is msec. int QTimer::start ( int msec, bool sshot = FALSE ) Starts the timer with a msec milliseconds timeout, and returns the ID of the timer, or zero when starting the timer failed. If sshot is TRUE, the timer will be activated only once; otherwise it will continue until it is stopped. Any pending timer will be stopped. See also singleShot(), stop(), changeInterval(), and isActive(). Examples: void QTimer::stop () Stops the timer. See also start(). Examples: void QTimer::timeout () [signal] This signal is emitted when the timer is activated. Examples: int QTimer::timerId () const Returns the ID of the timer if the timer is running; otherwise returns -1. SEE ALSO
http://doc.trolltech.com/qtimer.html http://www.trolltech.com/faq/tech.html COPYRIGHT
Copyright 1992-2001 Trolltech AS, http://www.trolltech.com. See the license file included in the distribution for a complete license statement. AUTHOR
Generated automatically from the source code. BUGS
If you find a bug in Qt, please report it as described in http://doc.trolltech.com/bughowto.html. Good bug reports help us to help you. Thank you. The definitive Qt documentation is provided in HTML format; it is located at $QTDIR/doc/html and can be read using Qt Assistant or with a web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially supported by Trolltech. If you find errors in this manual page, please report them to qt-bugs@trolltech.com. Please include the name of the manual page (qtimer.3qt) and the Qt version (3.1.1). Trolltech AS 9 December 2002 QTimer(3qt)
All times are GMT -4. The time now is 10:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy