Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Server hog
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{citations needed|date=November 2013}} '''Server (or resource) hogging''' is where a user, program or system places excessive load on a [[Server (computing)|server]]. "Hogging" aims to significantly degrade performance experienced for clients so that the server & resources itself are so heavily loaded that it fails to perform routine functions. ==History== In the early years of [[time-sharing]] computer systems in the 1960s it was common for a single institutional [[mainframe computer|mainframe]] to control many interactive terminals. In such an environment server [[Latency (engineering)|lag]] is acutely perceived. Furthermore, in many operating environments, scarce server resources such as CPU-seconds were often metered and charged against the account of the user running the program. An unintentional server hog could prove extremely costly in financial terms. These programs were often called run-away programs or endless loops. ==Resource contention== Server performance has many dimensions. Any subsystem that becomes excessively loaded can compromise the performance of other clients contending for that subsystem. Common forms of hardware contention include CPU cycles, interrupt latency, I/O bandwidth, available system memory, or aggregate system memory bandwidth. At the software level, contention can arise for [[buffer (computer science)|buffers]], [[queue (data structure)|queues]], [[spooling|spool]]s, or [[page table]]s. ==Known hogs== It is an accepted practice that servers are appropriately sized by system administrators for the workload (or mixture of workloads) expected, and server performance is closely monitored to establish performance baselines. The server load might include well known server hogs, such as system backup. These tasks are generally scheduled for time periods of light demand, such as in the very early hours on a Sunday morning, with an accepted administrative policy to discourage or prohibit other demands on the server during those time periods. ==Unexpected hogs== More often, the term server hog is used to designate an unusual load condition where the server performance falls short of the culturally accepted baseline. A common scenario in the early years of computing was an overload condition known as [[Thrashing (computer science)|thrashing]] where the aggregate server performance becomes severely degraded, such as when two departments of a large company attempt to run a heavy report concurrently on the same mainframe. In such a situation, the designation of the server hog becomes a political matter of pointing fingers, as the termination of either long-running report would restore the server to normal performance. ==Internet era== In the [[internet]] era, the nature of server loads greatly changed, as the clients became increasingly dispersed geographically, and often increasingly anonymous, as for example, any member of the public with internet access can request a web server in any part of the world to deliver a web page. In this context, a server hog most commonly designates a malicious server hogβa program written expressly for the purpose of overloading a remote server with excessive requests or excessively difficult requests (such as complex search). Use of a deliberate server hog is known as a [[denial-of-service attack]], a behaviour exhibited by many [[Computer virus|viruses]], [[Computer worm|worms]] and [[Trojan horse (computing)|trojan horses]]. It is also possible for a petulant or vindictive computer user to manually overload a remote server by unleashing a [[Meow Wars|crap flood]]. ==Bots== A special case is that of a run-away [[Internet bot|bot]], a program that was designed to be helpful by automating a drudgerous task, but due to poor programming or poorly understood circumstances, goes out of control and hammers a server unceasingly at a high rate. A common case is a [[web spider]] which accesses too many pages on a web server too quickly at the expense of the server's intended audience. ==References== [[Category:Scheduling (computing)]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Citations needed
(
edit
)