GB2366891A - Performance management with threshold of CPU usage - Google Patents

Performance management with threshold of CPU usage Download PDF

Info

Publication number
GB2366891A
GB2366891A GB0129221A GB0129221A GB2366891A GB 2366891 A GB2366891 A GB 2366891A GB 0129221 A GB0129221 A GB 0129221A GB 0129221 A GB0129221 A GB 0129221A GB 2366891 A GB2366891 A GB 2366891A
Authority
GB
United Kingdom
Prior art keywords
cpu
cpu usage
thread
terminal server
performance management
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
GB0129221A
Other versions
GB2366891B (en
GB0129221D0 (en
Inventor
Mark Austin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AppSense Ltd
Original Assignee
AppSense Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to GB0129221A priority Critical patent/GB2366891B/en
Application filed by AppSense Ltd filed Critical AppSense Ltd
Publication of GB0129221D0 publication Critical patent/GB0129221D0/en
Publication of GB2366891A publication Critical patent/GB2366891A/en
Application granted granted Critical
Publication of GB2366891B publication Critical patent/GB2366891B/en
Priority to US10/309,042 priority patent/US7302687B2/en
Priority to ES02258408T priority patent/ES2312527T3/en
Priority to EP02258408A priority patent/EP1329811B1/en
Priority to DE60228815T priority patent/DE60228815D1/en
Priority to AT02258408T priority patent/ATE408187T1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G06F11/3419—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment by assessing time
    • G06F11/3423—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment by assessing time where the assessed time is active or idle time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G06F11/3433—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment for load management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/81—Threshold

Abstract

A terminal server (6-12, fig 1) apparatus with a plurality of computer nodes (14-20, fig 1) is provided with performance management software (26, fig 1) to monitor demands made upon central processing units (CPU) from each computer node. The performance manager samples the CPU usage at a predetermined rate and if a threshold of CPU usage has been breached for a number of sample cycles then the load on the CPU is reduced. The load on the CPU is reduced by selecting a thread or threads which are occupying a significant percentage of CPU load, typically over 5%, and then the performance manager temporarily suspends each selected thread for a fraction of a second. The usage threshold is normally 100% of the CPU capacity.

Description

<Desc/Clms Page number 1> Improvements In and Relating to Computer Apparatus, Terminal Server Apparatus & Performance Management Methods Therefor Field of the Invention The present invention relates to computer apparatus, terminal server apparatus and to performance management methods therefore.
Background to the Invention A terminal server environment consist of one or more terminal servers to which are networked (by any suitable connection) a plurality of thin client computer nodes. Application execution, data processing and, usually, data storage occur on the terminal servers. The user's thin client computer node acts primarily as a graphical user interface and does not carry out substantive application processing. Currently implementations of this environment include Windows 2000 Terminal Services, Windows NT4.0 Terminal Server (WTS) and MetaFrame (trade mark), the last of these working with the WTS. The MetaFrame implementation permits files to be stored locally on a user's computer node, whereas WTS does not.
In operation, each user logs on to a separate session with the terminal servers. Each user node uses a varying amount of terminal server central processing unit (CPU) time, or cycles. The amount of CPU time used, for instance, by a word processing application during normal typing tends to be quite small. However, if the user instructs the word processors to perform an intensive
<Desc/Clms Page number 2>
task, such as a complex macro, the application may use all of the available CPU capacity to perform the task as quickly as possible. A given application being utilised by a user's computer node typically will use a plurality of threads to interface with the CPU within any given process.
Where a computer is dedicated to a single user this is usually acceptable behaviour. However, for a terminal server environment, which is accessed concurrently by many users, this behaviour can become problematic, especially when several processes are performing CPU intensive tasks. Subsequently, all users logged on to the terminal servers will encounter performance issues and unresponsive sessions. During long periods of unresponsiveness the server can become unstable, which is particularly problematic as the system administrator will be unable to determine the cause and resolve the issue due to the unresponsiveness of the server.
It is an aim of preferred embodiments of the present invention to obviate or overcome a disadvantage of the prior art, whether referred to herein or otherwise.
Summary of the Invention According to the present invention in a first aspect, there is provided a computer apparatus comprising a central processing unit (CPU), means for monitoring CPU load, and means for reducing the CPU usage from at least one CPU demand source, thereby to reduce the CPU load, if the CPU monitoring means determines that a predetermined threshold CPU usage is at least reached.
<Desc/Clms Page number 3>
Suitably, the CPU monitoring means comprises a CPU sampler. Suitably, the CPU sampler samples the CPU usage at a predetermined rate.
Suitably, the predetermined threshold must be at least reached for a plurality of samples before the CPU usage reducing means is activated.
Suitably, the predetermined threshold is 100% of the CPU capacity.
Suitably, the CPU usage reducing means comprises a thread clamper. A thread is clamped by limiting the amount of CPU capacity available to that thread. Suitably, a thread is clamped by temporarily suspending the relevant thread. Suitably, a thread is clamped by or to a predetermined percentage.
Suitably, the apparatus further comprises means for determining a thread to be clamped. Suitably, the thread determining means comprises means for determining the CPU usage of a process of which a thread forms a part and in which the CPU usage reducing means is only activated for the process if the CPU usage of the process at least reaches a predetermined threshold. Suitably, the thread determining means comprises means for determining the CPU usage of a thread and in which the CPU usage reducing means is only activated for the thread if the CPU usage of the thread at least reaches a predetermined threshold.
Suitably, the computer apparatus is a terminal server for connecting to a plurality of user computer nodes.
<Desc/Clms Page number 4>
Suitably, each user is regarded as a CPU demand source. Suitably, the terminal server comprises part of a server farm.
According to the present invention in a second aspect, there is provided a performance management method for a computer apparatus comprising a central processing unit (CPU), the method comprising the steps of monitoring the CPU usage and reducing the CPU usage from at least one CPU demand source if the CPU usage at least reaches a predetermined threshold.
Suitably, the CPU usage is sampled at a predetermined rate.
Suitably, the predetermined threshold must be at least reached for a plurality of samples before the CPU usage is reduced.
Suitably, the predetermined threshold is 1000 of the CPU capacity.
Suitably, the CPU usage is reduced by thread clamping. Suitably, a thread is clamped by temporarily suspending the relevant thread. Suitably, a thread is clamped by or to a predetermined percentage.
Suitably, a thread to be clamped is selectively determined. Suitably, the method further comprises determining the CPU usage of a process of which a thread forms a part and the CPU usage is only reduced for the
<Desc/Clms Page number 5>
process if the CPU usage of the process at least reaches a predetermined threshold. Suitably, the method further comprises determining the CPU usage of a thread and in which the CPU usage is only reduced for the thread if the CPU usage of the thread at least reaches a predetermined threshold.
Suitably, a thread is clamped for a predetermined period. Suitably, a user or group of users is allocated a CPU usage allocation below which CPU usage will not be reduced.
Suitably, after reducing CPU usage, if the CPU usage still at least reaches a predetermined value, CPU usage is further reduced until it is below a predetermined value. Suitably, the computer apparatus is a terminal server for connecting to a plurality of user computer nodes. Suitably, the terminal server comprises part of a server farm.
Suitably, each user is regarded as a CPU demand source. According to the present invention in a third aspect, there is provided a terminal server apparatus comprising a terminal server for connecting to a plurality of user computer nodes, the terminal server comprising_ a central processing unit (CPU), means for monitoring CPU load, and means for reducing the CPU usage from at least one user, thereby to reduce the CPU load, if the CPU monitoring
<Desc/Clms Page number 6>
means determines that a predetermined threshold CPU usage is at least reached.
Suitably, the terminal server comprises part of a server farm.
Suitably, the CPU monitoring means comprises a CPU sampler. Suitably, the CPU sampler samples the CPU usage at a predetermined rate.
Suitably, the. predetermined threshold must be at least reached for a plurality of samples before the CPU usage reducing means is activated.
Suitably, the predetermined threshold is 100% of the CPU capacity.
Suitably, the CPU usage reducing means comprises a thread clamper. A thread is clamped by limiting the amount of CPU capacity available to that thread. Suitably, a thread is clamped by temporarily suspending the relevant thread. Suitably, a thread is clamped by or to a predetermined percentage.
Suitably, the apparatus further comprises means for determining a thread to be clamped. Suitably, the thread determining means comprises means for determining the CPU usage of a process of which a thread forms a part and in which the CPU usage reducing means is only activated for the process if the CPU usage of the process at least reaches a predetermined threshold. Suitably, the thread determining means comprises means for determining the CPU usage of a thread and in which the CPU usage reducing
<Desc/Clms Page number 7>
means is only activated for the thread if the CPU usage of the thread at least reaches a predetermined threshold. According to the present invention in a fourth aspect, there is provided a performance management method for a terminal server apparatus comprising a terminal server for connecting to a plurality of user computer nodes, the terminal server comprising a central processing unit (CPU), the method comprising the steps of monitoring the CPU usage and reducing the CPU usage from at least one user if the CPU usage at least reaches a predetermined threshold.
Suitably, the terminal server comprises part of a server farm.
Suitably, the CPU usage is sampled at a predetermined rate.
Suitably, the predetermined threshold must be at least reached for a plurality of samples before the CPU usage is reduced.
Suitably, the predetermined threshold is 1000 of the CPU capacity.
Suitably, the, CPU usage is reduced by thread clamping. Suitably, a thread is clamped by temporarily suspending the relevant thread. Suitably, a thread is clamped by or to a predetermined percentage.
Suitably, a thread to be clamped is selectively determined. Suitably, the method further comprises
<Desc/Clms Page number 8>
determining the CPU usage of a process of which a thread forms a part and the CPU usage is only reduced for the process if the CPU usage of the process at least reaches a predetermined threshold. Suitably, the method further comprises determining the CPU usage of a thread and in which the CPU usage is only reduced for the thread if the CPU usage of the thread at least reaches a predetermined threshold.
Suitably, a thread is clamped for a predetermined period. Suitably, a user or group of users is allocated a CPU usage allocation below which CPU usage will not be reduced.
Suitably, after reducing CPU usage, if the CPU usage still at least reaches a predetermined value, CPU usage is further reduced until it is below a predetermined value. Brief Description of the Drawings The present invention will now be described, by way of example only, with reference to the drawings that follow; in which: Figure 1 is a schematic illustration of a terminal server environment according to the present invention.
Figure 2 is a schematic illustration of a performance manager of Figure 1.
Figure 3 is a functional flow diagram illustrating operation of the present invention.
<Desc/Clms Page number 9>
Figure 4 is a schematic illustration of a computer apparatus according to the present invention.
Description of the Preferred Embodiments Referring to Figure 1 of the drawings that follow, there is shown a terminal server apparatus 2 comprising a server farm indicated schematically at 4, comprising a plurality of terminal servers 6, 8, 10, 12.
The terminal servers 6-12 of server farm 4 are networked to a plurality of user computer nodes such as user computer nodes 14, 16, 18, 20. User computer nodes 14-20 are typically computer terminals, but may be other networkable graphical user interfaces. User computer nodes 14-18 are networked to a terminal server 6, 8, 10 or 12 via the internet, indicated schematically at 22 whereas user node 20 has a local area network direct connection 24 to a terminal server 6-12. Other users are networked to other terminal servers in the server farm 4.
Performance management software, indicated schematically at 26 is present and executed separately on each terminal server 6-12 as described below.
In use, users log on through user nodes 14-20 to a terminal server 6-12 where applications are executed and data stored for the use of user nodes 14-20. Each user node 14-20 is regarded as a source of CPU demand for the applications and processes for which it seeks CPU time from the relevant terminal server 6-12.
<Desc/Clms Page number 10>
Referring to Figure 2 of the drawings that follow, there is shown, as part of the performance manager software 26 a CPU sampler 28 and a CPU thread clamper 30. The CPU is indicated schematically at 32.
Referring to Figure 3 of the drawings that follow, operation of this embodiment of the present invention will now be described.
Initially, the following parameter variables are defined:
Parameter Description sample_period (seconds) This is the rate at which CPU samples will be collected. samples before_clamping If the system CPU load remains (integer) at 100% for this number of samples then the performance manager will look for appropriate threads to clamp. minimum_process_cpu (%) The performance manager will never clamp threads that belong to a process that is consuming less than this percentage of the system CPU. mimimum thread cpu (o) The performance manager will never clamp threads that are consuming less than this percentage of the system CPU. samples-to-clamp Once the performance manager has (integer) started to clamp threads, this value instructs the performance
<Desc/Clms Page number 11>
manager to clamp the threads for this number of samples before releasing them. clamp-quantity (o) The performance manager will clamp threads by this percentage of the CPU capacity. These parameters may be adjusted by the system administrator.
In step 300, CPU sampler 28 collects "sample period" samples per second. In step 302 it is determined whether clamping is required. Clamping is determined to be required if for "samples before clamping" samples the CPU load remains at the predetermined value of 1000. Other CPU usage may be set, to avoid usage reaching 100% if desired. By way of example, a "sample before clamping" value of 3, with a "sample_period" of 1 will instruct the performance manager 26 to start clamping threads if the system CPU load remains at 100% for three seconds.
If clamping is not required, the process returns to sampling the CPU load (step 300). If, however, clamping is required, in step 304 it is determined which of the threads currently using CPU capacity is/are to be clamped. Any given process may include a plurality of threads therein. To enable both processes and threads within them to be assessed for clamping, first the sampler determines whether the CPU load for a given process exceeds the "minimum-Process CPU" value. If the "minimum_process CPU". value is not exceeded the performance manager 26 will not
<Desc/Clms Page number 12>
clamp the threads within that process regardless of the amount of CPU load the individual threads are using.
The performance manager will only clamp threads that are occupying a significant percentage of the CPU load. The performance manager compares the sampled CPU load for a given thread with the "minimum process CPU" variable and will only clamp the corresponding thread if the CPU load exceeds that percentage.
Typical values for "minimum_process-cpu" and "minimum thread cpu" are 50.
Once one or more threads has or have been determined to be clamped, the performance manager will (step 306) clamp the thread or threads by the "clamp-quantity" percentage of the CPU capacity for a predetermined period, being the "samples_to clamp" number of samples before releasing them, say 10 samples.
The performance manager CPU thread clamper 30 clamps threads by suspending and resuming threads at extremely small intervals (typically, millisecond rates). For instance, to clamp a set of threads at 950, the performance manager will suspend and resume the set of threads over a short period of time (a fraction of a second) and will ensure that the threads are suspended for 50 of this time, making it impossible for the clamped threads to consume any more than 950 of the overall CPU between them. By only suspending threads for millisecond periods, those sessions in which threads are being clamped will avoid jerky responses and the clamping will hardly be noticeable to the user.
<Desc/Clms Page number 13>
Sampling then reoccurs to determine whether additional clamping is required.
Thus the performance manager 26 will only clamp threads when the total system CPU load remains at 1000 of the number of samples defined in the "samples before-clamping" parameter. Once one or more sessions have been identified for clamping, the performance manager CPU thread clamper 30 will clamp any thread(s) in these sessions that are using more than the minimum levels of CPU capacity (defined by "minimumrprocess CPU" and "minimum thread CPU"). It will clamp these threads by a set amount ("clamp-quantity"). For instance if the "clamp-quantity" is 5 then the performance manager will clamp all the threads to be clamped by 50. This will ensure that all of the clamp threads are confined to 95% of the CPU capacity. If the spare CPU is consumed immediately then the performance manager will progressively apply heavier clamping, by again identifying the set of threads to clamp, but each time it will clamp by an additional "clamp-quantity" until the CPU 32 is not saturated. Once the CPU 32 has been clamped to the required level then the performance manager 26 will keep the clamp in place for the number of samples defined in the "samples-to-clamp" parameter. Once this period is complete the performance manager 26 will release the clamped threads. If however the CPU 32 returns to full load then the performance manager 26 will reapply the clamping algorithm immediately.
In a further embodiment of the present invention, each user or group of users can be assigned a CPU share factor.
<Desc/Clms Page number 14>
By default, all users have a share factor of 1. This share factor is used to determine which users are consuming too much CPU. The system account is also counted in the number of users and can also be given a factor, which also defaults to 1.
For example, if four users 14-20 are logged on to a terminal server 6-12 then there are five sessions in total, if the system account (not shown) is included. If a11 of the users have a default share factor of 1 then they are allocated 200 (1000/5) of the CPU capacity each by the performance manager 26 when it is determining which sessions to clamp. Therefore each user can use up to 20% of the overall CPU and performance manager will not clamp any threads within that particular sessions. Some users may be allocated a greater or lesser share if desired.
Although the present invention is intended primarily for use with terminal server applications, for which it is particularly advantageous, embodiments thereof, as shown in Figure 4 of the drawings that follow may be used with and for single computer node (eg desktop) devices. In Figure 4 a computer apparatus 34 comprises a user's computer node, which computer apparatus 34 comprises a CPU 36 and a performance manager application 38 therefor. The performance manager 38 operates as described above for terminal server applications, except in this case it monitors only local usage of the CPU 36 (CPU demand source) and the CPU runs applications and processes for the computer apparatus 34.
<Desc/Clms Page number 15>
The present invention can be implemented on a variety of operating systems, including UNIX, WINDOWS and MACINTOSH (trade marks).
The present invention is not limited to the described terminal server architecture.
By implementing preferred embodiments of the present invention application performance and responsiveness can be maintained.
The reader's attention is directed to a11 papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of a11 such papers and documents are incorporated herein by reference.
All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive.
Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.
<Desc/Clms Page number 16>
The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.
<Desc/Clms Page number 17>

Claims (1)

  1. Claims 1. A computer apparatus comprising a central processing unit (CPU), means for monitoring CPU load, and means for -reducing the CPU usage from at least one CPU demand source, thereby to reduce the CPU load, if the CPU monitoring means determines that a predetermined threshold CPU usage is at least reached. 2. A computer- apparatus according to claim 1, in which the CPU monitoring means comprises a CPU sampler. 3. A computer apparatus according to claim 2, in which the CPU sampler samples the CPU usage at a predetermined rate. 4. A computer apparatus according to any preceding claim, in which the predetermined threshold must be at least reached for a plurality of samples before the CPU usage reducing means is activated. 5. A computer apparatus according to any preceding claim, in which the predetermined threshold is 100% of the CPU capacity. 6. A computer apparatus according to any preceding claim, in which the CPU usage reducing means comprises a thread clamper. 7. A computer apparatus according to claim 6, in which a thread is clamped by temporarily suspending the relevant thread.
    <Desc/Clms Page number 18>
    8. A computer apparatus according to claim 6 or claim 7, in which a thread is clamped by or to a predetermined percentage. 9. A computer apparatus according to claim 6, in which the apparatus further comprises means for determining a thread to be clamped. 10. A computer apparatus according to claim 9, in which the thread determining means comprises means for determining the CPU usage of a process of which a thread forms a part and in which the CPU usage reducing means is only activated for the process if the CPU usage of the process at least reaches a predetermined threshold. 11. A computer apparatus according to claim 9, in which the thread determining means comprises means for determining the CPU usage of a thread and in which the CPU usage reducing means is only activated for the thread if the CPU usage of the thread at least reaches a predetermined threshold. 12. A computer apparatus according to any preceding claim, in which the computer apparatus is a terminal server for connecting to a plurality of user computer nodes. 13. A computer apparatus according to claim 12, in which each user is regarded as a CPU demand source. 14. A computer apparatus according to claim 12 or claim 13, in which the terminal server comprises part of a server farm.
    <Desc/Clms Page number 19>
    15. A performance management method for a computer apparatus comprising a central processing unit (CPU), the method comprising the steps of monitoring the CPU usage and reducing the CPU usage from at least one CPU demand source if the CPU usage at least reaches a predetermined threshold. 16. A performance management method for a computer apparatus -.according to claim 15, in which the CPU usage is sampled at a predetermined rate. 17. A performance management method for a computer apparatus according to claim 15 or claim 16, in which the predetermined threshold must be at least reached for a plurality of samples before the CPU usage is reduced. 18. A performance management method for a computer apparatus according to any one of claims 15 to 17, in which the predetermined threshold is 100% of the CPU capacity. 19. A performance management method for a computer apparatus according to any one of claims 15 to 18, in which the CPU usage is reduced by thread clamping. 20. A performance management method for a computer apparatus according to claim 19, in which a thread is clamped by temporarily suspending the relevant thread. 21. A performance management method for a computer apparatus according to claim 19 or claim 20, in which
    <Desc/Clms Page number 20>
    a thread is clamped by or to a predetermined percentage. 22. A performance management method for a computer apparatus according to any one of claims 19 to 21, in which a thread to be clamped is selectively determined. 23. A performance management method for a computer apparatus according to claim 22, in which the method further comprises determining the CPU usage of a process of which a thread forms a part and the CPU usage is only reduced for the process if the CPU usage of the process at least reaches a predetermined threshold. 24. A performance management method for a computer apparatus according to claim 22, in which the method further comprises determining the CPU usage of a thread and in which the CPU usage is only reduced for the thread if the CPU usage of the thread at least reaches a predetermined threshold. 25. A performance management method for a computer apparatus according to any one of claims 19 to 24, in which a thread is clamped for a predetermined period. 26. A performance management method for a computer apparatus according to any one of claims 15 to 25, in which a user or group of users is allocated a CPU usage allocation below which CPU usage will not be reduced.
    <Desc/Clms Page number 21>
    27. A performance management method for a computer apparatus according to any one of claims 15 to 26, in which after reducing CPU usage, if the CPU usage still at least reaches a predetermined value, CPU usage is further reduced until it is below a predetermined value. 28. A performance management method for a computer apparatus according to any one of claims 15 to 27, in which the -computer apparatus is a terminal server for connecting to a plurality of user computer nodes. 29. A performance management method for a computer apparatus according to claim 28, in which the terminal server comprises part of a server farm. 30. A performance management method for a computer apparatus according to claim 28 or claim 29, in which each user is regarded as a CPU demand source. 31. A terminal server apparatus comprising a terminal server for connecting to a plurality of user computer nodes, the terminal server comprising a central processing unit (CPU), means for monitoring CPU load, and means for reducing the CPU usage from at least one user, thereby to reduce the CPU load, if the CPU monitoring means determines that a predetermined threshold CPU usage is at least reached. 32. A terminal server apparatus according to claim 31, in which the terminal server comprises part of a server farm.
    <Desc/Clms Page number 22>
    33. A terminal server apparatus according to claim 31 or claim 32, in which the CPU monitoring means comprises a CPU sampler. 34. A terminal server apparatus according to claim 33, in which the CPU sampler samples the CPU usage at a predetermined rate. 35. A terminal server apparatus according to any one of claims 31 -to 34, in which the predetermined threshold must be at least reached for a plurality of samples before the CPU usage reducing means is activated. 36. A terminal server apparatus according to any one of claims 31 to 35 in which the predetermined threshold is 100% of the CPU capacity. 37. A terminal server apparatus according to any one of claims 31 to 36, in which the CPU usage reducing means comprises a thread clamper. 38. A terminal server apparatus according to claim 37, in which a thread is clamped by temporarily suspending the relevant thread. 39. A terminal server apparatus according to claim 37, in which a thread is clamped by or to a predetermined percentage. 40. A terminal server apparatus according to any one of claims 37 to 39, in which the apparatus further comprises means for determining a thread to be clamped.
    <Desc/Clms Page number 23>
    41. A terminal server apparatus according to claim 40, in which the thread determining means comprises means for determining the CPU usage of a process of which a thread forms a part and in which the CPU usage reducing means is only activated for the process if the CPU usage of the process at least reaches a predetermined threshold. 42. A terminal-server apparatus according to claim 40, in which the thread determining means comprises means for determining the CPU usage of a thread and in which the CPU usage reducing means is only activated for the thread if the CPU usage of the thread at least reaches a predetermined threshold. 43. A performance management method for a terminal server apparatus comprising a terminal server for connecting to a plurality of user computer nodes, the terminal server comprising a central processing unit (CPU), the method comprising the steps of monitoring the CPU usage and reducing the CPU usage from at least one user if the CPU usage at least reaches a predetermined threshold. 44. A performance management method for a terminal server apparatus according to claim 43, in which the terminal server comprises part of a server farm. 45. A performance management method for a terminal server apparatus according to claim 43 or claim 44, in which the CPU usage is sampled at a predetermined rate.
    <Desc/Clms Page number 24>
    46. A performance management method for a terminal server apparatus according to any one of claims 43 to 45, in which the predetermined threshold must be at least reached for a plurality of samples before the CPU usage is reduced. 47. A performance management method for a terminal server apparatus according to any one of claims 43 to 47, in which the predetermined threshold is 100% of the CPU capacity. -- 48. A performance management method for a terminal server apparatus according to any one o claims 43 to 47, in which the CPU usage is reduced by thread clamping. 49. A performance management method for a terminal server apparatus according to claim 48, in which a thread is clamped by temporarily suspending the relevant thread. 50. A performance management method for a terminal server apparatus according to claim 48, in which a thread is clamped by or to a predetermined percentage. 51. A performance management method for a terminal server apparatus according to any one of claims 48 to 50, in which a thread to be clamped is selectively determined. 52. A performance management method for a terminal server apparatus according to claim 51, in which the method further comprises determining the CPU usage of @a process of which a thread forms a part and the CPU usage is only reduced for the process if the CPU usage
    <Desc/Clms Page number 25>
    of the process at least reaches a predetermined threshold. 53. A performance management method for a terminal server apparatus according to claim 51, in which the method further comprises determining the CPU usage of a thread and in which the CPU usage is only reduced for the thread if the CPU usage of the thread at least reaches a predetermined threshold. 54. A performance management method for a terminal server apparatus according to any one of claims 48 to 53, in which a thread is clamped for a predetermined period. 55. A performance management method for a terminal server apparatus according to any one of claims 43 to 54, in which a user or group of users is allocated a CPU usage allocation below which CPU usage will not be reduced. 55. A performance management method for a terminal server apparatus according to any one of claims 43 to 55, in which after reducing CPU usage, if the CPU usage still at least reaches a predetermined value, CPU usage is further reduced until it is below a predetermined value. 57. A computer apparatus substantially as described herein, with reference to and as shown in the accompanying figures.
    <Desc/Clms Page number 26>
    58. A performance management method for a computer apparatus, substantially as described herein with reference to the accompanying figures. 59. A terminal server apparatus substantially as described herein, with reference to and as shown in the accompanying figures. 60. A performance management method for a terminal server apparatus, substantially as described herein, with reference to the accompanying figures.
GB0129221A 2001-12-06 2001-12-06 Improvements in and relating to computer apparatus terminal server apparatus & performance management methods therefor Expired - Lifetime GB2366891B (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
GB0129221A GB2366891B (en) 2001-12-06 2001-12-06 Improvements in and relating to computer apparatus terminal server apparatus & performance management methods therefor
US10/309,042 US7302687B2 (en) 2001-12-06 2002-12-04 Computer apparatus, terminal server apparatus and performance management methods therefor
AT02258408T ATE408187T1 (en) 2001-12-06 2002-12-05 METHOD AND DEVICE FOR DISTRIBUTING LOAD IN A COMPUTER SYSTEM
DE60228815T DE60228815D1 (en) 2001-12-06 2002-12-05 Method and device for load distribution in a computer system
EP02258408A EP1329811B1 (en) 2001-12-06 2002-12-05 Method and apparatus for balancing load in a computer system
ES02258408T ES2312527T3 (en) 2001-12-06 2002-12-05 PROCEDURE AND APPLIANCE TO REPAIR THE LOAD IN AN INFORMATIC SYSTEM.

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB0129221A GB2366891B (en) 2001-12-06 2001-12-06 Improvements in and relating to computer apparatus terminal server apparatus & performance management methods therefor

Publications (3)

Publication Number Publication Date
GB0129221D0 GB0129221D0 (en) 2002-01-23
GB2366891A true GB2366891A (en) 2002-03-20
GB2366891B GB2366891B (en) 2002-11-20

Family

ID=9927123

Family Applications (1)

Application Number Title Priority Date Filing Date
GB0129221A Expired - Lifetime GB2366891B (en) 2001-12-06 2001-12-06 Improvements in and relating to computer apparatus terminal server apparatus & performance management methods therefor

Country Status (6)

Country Link
US (1) US7302687B2 (en)
EP (1) EP1329811B1 (en)
AT (1) ATE408187T1 (en)
DE (1) DE60228815D1 (en)
ES (1) ES2312527T3 (en)
GB (1) GB2366891B (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1555613A1 (en) * 2003-03-31 2005-07-20 Fujitsu Limited Cpu use time counting method and job control device using the cpu use time
WO2006029656A1 (en) * 2004-09-13 2006-03-23 Fujitsu Siemens Computers, Inc. Computer arrangement for providing services for clients through a network
EP2087430A2 (en) * 2006-11-27 2009-08-12 Cisco Technology, Inc. Lock manager rotation in a multiprocessor storage area network
EP2097815A2 (en) * 2006-12-27 2009-09-09 More IT Resources Ltd. Method and system for transaction resource control
EP2396730A1 (en) * 2009-02-13 2011-12-21 Alexey Raevsky Devices and methods for optimizing data-parallel processing in multi-core computing systems
US8677014B2 (en) 2006-11-27 2014-03-18 Cisco Technology, Inc. Fine granularity exchange level load balancing in a multiprocessor storage area network

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8237386B2 (en) 2003-08-15 2012-08-07 Apple Inc. Methods and apparatuses for operating a data processing system
WO2005064472A2 (en) * 2003-12-23 2005-07-14 Unisys Corporation System and method for metering the performance of a data processing system
US7784054B2 (en) * 2004-04-14 2010-08-24 Wm Software Inc. Systems and methods for CPU throttling utilizing processes
EP1805619A4 (en) * 2004-10-04 2008-02-13 Research In Motion Ltd System and method for adaptive allocation of threads to user objects in a computer system
CA2577230C (en) * 2004-10-04 2014-12-30 Research In Motion Limited Allocation of threads to user objects in a computer system
US7793291B2 (en) * 2004-12-22 2010-09-07 International Business Machines Corporation Thermal management of a multi-processor computer system
JP4367856B2 (en) * 2005-07-07 2009-11-18 レノボ シンガポール プライヴェート リミテッド Process control system and control method thereof
US8117505B2 (en) * 2005-11-07 2012-02-14 Microsoft Corporation Resource exhaustion prediction, detection, diagnosis and correction
JP2007199811A (en) * 2006-01-24 2007-08-09 Hitachi Ltd Program control method, computer and program control program
JP2008102778A (en) * 2006-10-19 2008-05-01 Fujitsu Ltd Information processor, control method of information processor and program
US20080276299A1 (en) * 2007-04-02 2008-11-06 Samsung Electronics Co., Ltd. Wireless terminal apparatus and method of protecting system resources
US7720643B1 (en) 2007-09-24 2010-05-18 United Services Automobile Association (Usaa) Estimating processor usage
US7680628B1 (en) * 2007-09-24 2010-03-16 United Services Automobile Association (Usaa) Estimating processor usage
US7725296B1 (en) 2007-09-24 2010-05-25 United Services Automobile Association (Usaa) Estimating processor usage
US7530072B1 (en) * 2008-05-07 2009-05-05 International Business Machines Corporation Method to segregate suspicious threads in a hosted environment to prevent CPU resource exhaustion from hung threads
US8656396B2 (en) * 2009-08-11 2014-02-18 International Business Machines Corporation Performance optimization based on threshold performance measure by resuming suspended threads if present or by creating threads within elastic and data parallel operators
US7925874B1 (en) 2010-05-18 2011-04-12 Kaspersky Lab Zao Adaptive configuration of conflicting applications
JP6056453B2 (en) * 2012-12-20 2017-01-11 富士通株式会社 Program, data management method, and information processing apparatus
US9106391B2 (en) 2013-05-28 2015-08-11 International Business Machines Corporation Elastic auto-parallelization for stream processing applications based on a measured throughput and congestion
KR20180013608A (en) 2016-07-29 2018-02-07 삼성전자주식회사 Method and apparatus for reducing power consumption of electronic device
CN109344039A (en) * 2018-09-13 2019-02-15 郑州云海信息技术有限公司 A kind of host intelligent control method and device
CN111427693B (en) * 2020-03-26 2023-04-28 北京字节跳动网络技术有限公司 Data processing method, system, medium, service system and bypass unloading system
CN112346933B (en) * 2020-11-09 2023-03-17 深信服科技股份有限公司 Malicious file scanning method, device, equipment and medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000284976A (en) * 1999-03-31 2000-10-13 Nec Corp Cpu load control method and its device
JP2000322365A (en) * 1999-05-12 2000-11-24 Hitachi Ltd Acceptance limiting method for server computer

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5475844A (en) * 1992-11-27 1995-12-12 Nec Corporation Heavily loaded resource evaluation system
US5752031A (en) * 1995-04-24 1998-05-12 Microsoft Corporation Queue object for controlling concurrency in a computer system
US5996083A (en) 1995-08-11 1999-11-30 Hewlett-Packard Company Microprocessor having software controllable power consumption
JPH09167141A (en) * 1995-12-18 1997-06-24 Hitachi Ltd Load distribution control method
US6182109B1 (en) * 1996-03-08 2001-01-30 International Business Machines Corporation Dynamic execution unit management for high performance user level network server system
US5809235A (en) * 1996-03-08 1998-09-15 International Business Machines Corporation Object oriented network event management framework
US6237024B1 (en) * 1998-03-20 2001-05-22 Sun Microsystem, Inc. Method and apparatus for the suspension and continuation of remote processes
US5872972A (en) * 1996-07-05 1999-02-16 Ncr Corporation Method for load balancing a per processor affinity scheduler wherein processes are strictly affinitized to processors and the migration of a process from an affinitized processor to another available processor is limited
US6026425A (en) * 1996-07-30 2000-02-15 Nippon Telegraph And Telephone Corporation Non-uniform system load balance method and apparatus for updating threshold of tasks according to estimated load fluctuation
US6067557A (en) * 1996-09-06 2000-05-23 Cabletron Systems, Inc. Method and system for allocating CPU bandwidth by prioritizing competing processes
US6581104B1 (en) * 1996-10-01 2003-06-17 International Business Machines Corporation Load balancing in a distributed computer enterprise environment
KR100209464B1 (en) * 1996-11-30 1999-07-15 김영환 Dynamic overload controlling method and apparatus in the digital mobile communication system
US6269391B1 (en) * 1997-02-24 2001-07-31 Novell, Inc. Multi-processor scheduling kernel
US6397252B1 (en) * 1997-12-19 2002-05-28 Electronic Data Systems Corporation Method and system for load balancing in a distributed object system
US6182022B1 (en) 1998-01-26 2001-01-30 Hewlett-Packard Company Automated adaptive baselining and thresholding method and system
US6477561B1 (en) * 1998-06-11 2002-11-05 Microsoft Corporation Thread optimization
US6707792B1 (en) * 1998-06-30 2004-03-16 Cisco Technology, Inc. Overload reduction in a communication system
US6665272B1 (en) * 1999-09-30 2003-12-16 Qualcomm Incorporated System and method for persistence-vector-based modification of usage rates
US6564328B1 (en) 1999-12-23 2003-05-13 Intel Corporation Microprocessor with digital power throttle
US6845456B1 (en) * 2001-05-01 2005-01-18 Advanced Micro Devices, Inc. CPU utilization measurement techniques for use in power management

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000284976A (en) * 1999-03-31 2000-10-13 Nec Corp Cpu load control method and its device
JP2000322365A (en) * 1999-05-12 2000-11-24 Hitachi Ltd Acceptance limiting method for server computer

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1555613A1 (en) * 2003-03-31 2005-07-20 Fujitsu Limited Cpu use time counting method and job control device using the cpu use time
EP1555613A4 (en) * 2003-03-31 2009-04-15 Fujitsu Ltd Cpu use time counting method and job control device using the cpu use time
WO2006029656A1 (en) * 2004-09-13 2006-03-23 Fujitsu Siemens Computers, Inc. Computer arrangement for providing services for clients through a network
EP2087430A2 (en) * 2006-11-27 2009-08-12 Cisco Technology, Inc. Lock manager rotation in a multiprocessor storage area network
EP2087430A4 (en) * 2006-11-27 2010-10-27 Cisco Tech Inc Lock manager rotation in a multiprocessor storage area network
US8677014B2 (en) 2006-11-27 2014-03-18 Cisco Technology, Inc. Fine granularity exchange level load balancing in a multiprocessor storage area network
EP2097815A2 (en) * 2006-12-27 2009-09-09 More IT Resources Ltd. Method and system for transaction resource control
EP2097815A4 (en) * 2006-12-27 2011-05-25 More It Resources Ltd Method and system for transaction resource control
US9582337B2 (en) 2006-12-27 2017-02-28 Pivotal Software, Inc. Controlling resource consumption
EP2396730A1 (en) * 2009-02-13 2011-12-21 Alexey Raevsky Devices and methods for optimizing data-parallel processing in multi-core computing systems
EP2396730A4 (en) * 2009-02-13 2013-01-09 Alexey Raevsky Devices and methods for optimizing data-parallel processing in multi-core computing systems

Also Published As

Publication number Publication date
EP1329811B1 (en) 2008-09-10
ES2312527T3 (en) 2009-03-01
US20030126184A1 (en) 2003-07-03
ATE408187T1 (en) 2008-09-15
GB2366891B (en) 2002-11-20
EP1329811A2 (en) 2003-07-23
GB0129221D0 (en) 2002-01-23
EP1329811A3 (en) 2004-08-18
US7302687B2 (en) 2007-11-27
DE60228815D1 (en) 2008-10-23

Similar Documents

Publication Publication Date Title
GB2366891A (en) Performance management with threshold of CPU usage
US7080378B1 (en) Workload balancing using dynamically allocated virtual servers
US7644321B2 (en) Autonomically adjusting configuration parameters for a server when a different server fails
US9154549B2 (en) Dynamic server farms
US6154849A (en) Method and apparatus for resource dependency relaxation
US7930397B2 (en) Remote dynamic configuration of a web server to facilitate capacity on demand
JP6495010B2 (en) System and method for active-passive routing and control of traffic in a traffic director environment
US9444699B2 (en) Scalable network monitoring system
US7702783B2 (en) Intelligent performance monitoring of a clustered environment
US8578030B2 (en) Autonomic assignment of communication buffers by aggregating system profiles
EP1949238A1 (en) Method and system for virtualized health monitoring of resources
CN110677274A (en) Event-based cloud network service scheduling method and device
CN109800261B (en) Dynamic control method and device for double-database connection pool and related equipment
US20220070099A1 (en) Method, electronic device and computer program product of load balancing
CN108228393A (en) A kind of implementation method of expansible big data High Availabitity
US7287086B2 (en) Methods, systems and computer program products for controlling data transfer for data replication or backup based on system and/or network resource information
CN105162823A (en) Virtual machine management method and device
CN110868323B (en) Bandwidth control method, device, equipment and medium
US9755897B1 (en) Enhanced throttle management system
US20040243706A1 (en) Method and system for balancing the load of a computer resource among computers
US20080163169A1 (en) System and method for managing code displacement
JP2007179246A (en) Method, program and server for computer management
CN111988234A (en) Overload protection method, device, server and storage medium
JP2003084989A (en) Priority dynamic control system, priority dynamic control method, and priority dynamic control program
EP1145496A2 (en) A method to monitor and control server applications using low cost covert channels

Legal Events

Date Code Title Description
732E Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)

Free format text: REGISTERED BETWEEN 20160602 AND 20160608

732E Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)

Free format text: REGISTERED BETWEEN 20201008 AND 20201014

PE20 Patent expired after termination of 20 years

Expiry date: 20211205