You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 44.223.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 23:54, 31 July 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪AntiCompositeNumber‬. The reason given is Open proxy/Webhost: Visit the FAQ if you are affected .
- Start of block: 13:57, 18 August 2022
- Expiry of block: 13:57, 18 November 2024
Your current IP address is 44.223.83.3. The blocked range is 44.223.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((citations needed|date=November 2013))

A '''server hog''' is a user, program or system that places excessive load on a [[Server (computing)|server]] such that the server performance as experienced by other [[client (computing)|clients]] is degraded, or such that the server itself is so heavily loaded that it fails to perform routine housekeeping for its own maintenance.

==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)]]

Pages transcluded onto the current version of this page (help):

Template:Ambox (view source) (template editor protected)
Template:Citations needed (view source) (semi-protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:More citations needed (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Server hog.

Retrieved from "https://en.wikipedia.org/wiki/Server_hog"