SPEC INT is a computer benchmark specification for CPU integer processing power. It is maintained by the Standard Performance Evaluation Corporation (SPEC). SPEC INT is the integer performance testing component of the SPEC test suite. The first SPEC test suite, CPU92, was announced in 1992. It was followed by CPU95, CPU2000, and CPU2006. The latest standard is SPEC CPU 2017 and consists of SPEC speed and SPEC rate (aka SPECCPU_2017).
35-453: CPU2006 is a set of benchmarks designed to test the CPU performance of a modern server computer system. It is split into two components, the first being CINT2006, the other being CFP2006 ( SPECfp ), for floating point testing. SPEC defines a base runtime for each of the 12 benchmark programs. For SPECint2006, that number ranges from 1000 to 3000 seconds. The timed test is run on the system, and
70-1107: A computer monitor or input device, audio hardware and USB interfaces. Many servers do not have a graphical user interface (GUI). They are configured and managed remotely. Remote management can be conducted via various methods including Microsoft Management Console (MMC), PowerShell , SSH and browser-based out-of-band management systems such as Dell's iDRAC or HP's iLo . Large traditional single servers would need to be run for long periods without interruption. Availability would have to be very high, making hardware reliability and durability extremely important. Mission-critical enterprise servers would be very fault tolerant and use specialized hardware with low failure rates in order to maximize uptime . Uninterruptible power supplies might be incorporated to guard against power failure. Servers typically include hardware redundancy such as dual power supplies , RAID disk systems, and ECC memory , along with extensive pre-boot memory testing and verification. Critical components might be hot swappable , allowing technicians to replace them on
105-405: A computer network . This architecture is called the client–server model . Servers can provide various functionalities, often called "services", such as sharing data or resources among multiple clients or performing computations for a client. A single server can serve multiple clients, and a single client can use multiple servers. A client process may run on the same device or may connect over
140-598: A means to graphically represent data. DSDs provided a means to represent the relationships between different data entities. In 1970, Codd introduced the concept that users of a database should be ignorant of the "inner workings" of the database. Codd proposed the "relational view" of data which later evolved into the Relational Model which most databases use today. In 1971, the Database Task Report Group of CODASYL (the driving force behind
175-414: A network to a server on a different device. Typical servers are database servers , file servers , mail servers , print servers , web servers , game servers , and application servers . Client–server systems are usually most frequently implemented by (and often identified with) the request–response model: a client sends a request to the server, which performs some action and sends a response back to
210-401: A resource) is a server, and the calling process or processes is a client. Thus any general-purpose computer connected to a network can host servers. For example, if files on a device are shared by some process, that process is a file server . Similarly, web server software can run on any capable computer, and so a laptop or a personal computer can host a web server. While request–response
245-755: A server is used. Almost the entire structure of the Internet is based upon a client–server model. High-level root nameservers , DNS , and routers direct the traffic on the internet. There are millions of servers connected to the Internet, running continuously throughout the world and virtually every action taken by an ordinary Internet user requires one or more interactions with one or more servers. There are exceptions that do not use dedicated servers; for example, peer-to-peer file sharing and some implementations of telephony (e.g. pre-Microsoft Skype ). Hardware requirement for servers vary widely, depending on
280-618: Is a collaborative effort, Open Compute Project around this concept. A class of small specialist servers called network appliances are generally at the low end of the scale, often being smaller than common desktop computers. A mobile server has a portable form factor, e.g. a laptop . In contrast to large data centers or rack servers, the mobile server is designed for on-the-road or ad hoc deployment into emergency, disaster or temporary environments where traditional servers are not feasible due to their power requirements, size, and deployment time. The main beneficiaries of so-called "server on
315-427: Is also less of a concern, but power consumption and heat output can be a serious issue. Server rooms are equipped with air conditioning devices. A server farm or server cluster is a collection of computer servers maintained by an organization to supply server functionality far beyond the capability of a single device. Modern data centers are now often built of very large clusters of much simpler servers, and there
350-438: Is also typically disabled, A more complete system-level benchmark that allows all CPUs to be used is known as SPECint_rate2006, also called "CINT2006 Rate". The SPECint2006 test suite consists of 12 benchmark programs, designed to test exclusively the integer performance of the system. The benchmarks are: Server (computing) A server is a computer that provides information to other computers called " clients " on
385-454: Is closest to how a user would compile a program with standard flags. The 'peak' metric can be performed with maximum compiler optimization, even to the extent of different optimizations for each benchmark. This number represents maximum system performance, achieved by full compiler optimization. SPEC INT tests are carried out on a wide range of hardware, with results typically published for the full range of system-level implementations employing
SECTION 10
#1732772555561420-402: Is part of the client–server model ; in this model, a server serves data for clients . The nature of communication between a client and server is request and response . This is in contrast with peer-to-peer model in which the relationship is on-demand reciprocation. In principle, any computerized process that can be used or called by another process (particularly remotely, particularly to share
455-472: Is that of the CPU, RAM, and compiler , and does not test I/O , networking , or graphics . Two metrics are reported for a particular benchmark, "base" and "peak". Compiler options account for the difference between the two numbers. As the SPEC benchmarks are distributed as source code , it is up to the party performing the test to compile this code. There is agreement that the benchmarks should be compiled in
490-415: Is the most common client-server design, there are others, such as the publish–subscribe pattern . In the publish-subscribe pattern, clients register with a pub-sub server, subscribing to specified types of messages; this initial registration may be done by request-response. Thereafter, the pub-sub server forwards matching messages to the clients without any further requests: the server pushes messages to
525-654: The GNU General Public Licence include Ingres and MySQL . Every server uses its own query logic and structure. The SQL (Structured Query Language) query language is more or less the same on all relational database applications. For clarification, a database server is simply a server that maintains services related to clients via database applications. DB-Engines lists over 300 DBMSs in its ranking. The foundations for modeling large sets of data were first introduced by Charles Bachman in 1969. Bachman introduced Data Structure Diagrams (DSDs) as
560-847: The Internet, the dominant operating systems among servers are UNIX-like open-source distributions , such as those based on Linux and FreeBSD , with Windows Server also having a significant share. Proprietary operating systems such as z/OS and macOS Server are also deployed, but in much smaller numbers. Servers that run Linux are commonly used as Webservers or Databanks. Windows Servers are used for Networks that are made out of Windows Clients. Specialist server-oriented operating systems have traditionally had features such as: In practice, today many desktop and server operating systems share similar code bases , differing mostly in configuration. In 2010, data centers (servers, cooling, and other electrical infrastructure) were responsible for 1.1–1.5% of electrical energy consumption worldwide and 1.7–2.2% in
595-599: The United States. One estimate is that total energy consumption for information and communications technology saves more than 5 times its carbon footprint in the rest of the economy by increasing efficiency. Global energy consumption is increasing due to the increasing demand of data and bandwidth. Natural Resources Defense Council (NRDC) states that data centers used 91 billion kilowatt hours (kWh) electrical energy in 2013 which accounts to 3% of global electricity usage. Environmental groups have placed focus on
630-437: The abstract form of functionality, e.g. Web service . Alternatively, it may refer to a computer program that turns a computer into a server, e.g. Windows service . Originally used as "servers serve users" (and "users use servers"), in the sense of "obey", today one often says that "servers serve data", in the same sense as "give". For instance, web servers "serve [up] web pages to users" or "service their requests". The server
665-493: The carbon emissions of data centers as it accounts to 200 million metric tons of carbon dioxide in a year. Database server A database server is a server which uses a database application that provides database services to other computer programs or to computers , as defined by the client–server model . Database management systems (DBMSs) frequently provide database-server functionality, and some database management systems (such as MySQL ) rely exclusively on
700-421: The client, rather than the client pulling messages from the server as in request-response. The role of a server is to share data as well as to share resources and distribute work. A server computer can serve its own computer programs as well; depending on the scenario, this could be part of a quid pro quo transaction, or simply a technical possibility. The following table shows several scenarios in which
735-468: The client, typically with a result or acknowledgment. Designating a computer as "server-class hardware" implies that it is specialized for running servers on it. This often implies that it is more powerful and reliable than standard personal computers , but alternatively, large computing clusters may be composed of many relatively simple, replaceable server components. The use of the word server in computing comes from queueing theory , where it dates to
SECTION 20
#1732772555561770-537: The client–server model for database access (while others, like SQLite , are meant for use as an embedded database ). Users access a database server either through a " front end " running on the user's computer – which displays requested data – or through the " back end ", which runs on the server and handles tasks such as data analysis and storage. In a master–slave model, database master servers are central and primary locations of data while database slave servers are synchronized backups of
805-415: The common sense of a process performing service for requests, usually remote, with the 1981 version reading: SERVER n. A kind of DAEMON which performs a service for the requester, which often runs on a computer other than the one on which the server runs. The average utilization of a server in the early 2000s was 5 to 15%, but with the adoption of virtualization this figure started to increase to reduce
840-411: The data structure set were similar and "congruent" ways of structuring data while working for Honeywell . The entity–relationship model was first proposed in its current form by Peter Chen in 1976 while he was conducting research at MIT . This model became the most frequently used model to describe relational databases. Chen was able to propose a model that was superior to the navigational model and
875-410: The development of the programming language COBOL ) first proposed a "data description language for describing a database, a data description language for describing that part of the data base known to a program, and a data manipulation language." Most of the research and development of databases focused on the relational model during the 1970s. In 1975, Bachman demonstrated how the relational model and
910-411: The go" technology include network managers, software or database developers, training centers, military personnel, law enforcement, forensics, emergency relief groups, and service organizations. To facilitate portability, features such as the keyboard , display , battery ( uninterruptible power supply , to provide power redundancy in case of failure), and mouse are all integrated into the chassis. On
945-530: The latest CPUs. For SPECint2006, the CPUs include Intel and AMD x86 & x86-64 processors, Sun SPARC CPUs, IBM Power CPUs, and IA-64 CPUs. This range of capabilities, specifically in this case the number of CPUs, means that the SPEC INT benchmark is usually run on only a single CPU, even if the system has many CPUs. If a single CPU has multiple cores , only a single core is used; hyper-threading
980-430: The master acting as proxies . Most database applications respond to a query language . Each database understands its query language and converts each submitted query to server-readable form and executes it to retrieve results. Examples of proprietary database applications include Oracle , IBM Db2 , Informix , and Microsoft SQL Server . Examples of free software database applications include PostgreSQL ; and under
1015-742: The mid 20th century, being notably used in Kendall (1953) (along with "service"), the paper that introduced Kendall's notation . In earlier papers, such as the Erlang (1909) , more concrete terms such as "[telephone] operators" are used. In computing, "server" dates at least to RFC 5 (1969), one of the earliest documents describing ARPANET (the predecessor of Internet ), and is contrasted with "user", distinguishing two types of host : "server-host" and "user-host". The use of "serving" also dates to early documents, such as RFC 4, contrasting "serving-host" with "using-host". The Jargon File defines server in
1050-494: The number of servers needed. Strictly speaking, the term server refers to a computer program or process (running program). Through metonymy , it refers to a device used for (or a device dedicated to) running one or several server programs. On a network, such a device is called a host . In addition to server , the words serve and service (as verb and as noun respectively) are frequently used, though servicer and servant are not. The word service (noun) may refer to
1085-400: The ratio is 4.885. Each ratio is computed, and then the geometric mean of those ratios is computed to produce an overall value. For a fee, SPEC distributes source code files to users wanting to test their systems. These files are written in a standard programming language , which is then compiled for each particular CPU architecture and operating system . Thus, the performance measured
SPECint - Misplaced Pages Continue
1120-564: The running server without shutting it down, and to guard against overheating, servers might have more powerful fans or use water cooling . They will often be able to be configured, powered up and down, or rebooted remotely, using out-of-band management , typically based on IPMI . Server casings are usually flat and wide , and designed to be rack-mounted, either on 19-inch racks or on Open Racks . These types of servers are often housed in dedicated data centers . These will normally have very stable power and Internet and increased security. Noise
1155-425: The same way as a user would compile a program, but there is no consistent method for user compilation, it varies system by system. SPEC, in this case, defines two reference points, "base" and "peak". Base has a more strict set of compilation rules than peak. Less optimization can be done, the compiler flags must be the same for each benchmark, in the same order, and there must be a limited number of flags. Base, then,
1190-412: The server's purpose and its software. Servers often are more powerful and expensive than the clients that connect to them. The name server is used both for the hardware and software pieces. For the hardware servers, it is usually limited to mean the high-end machines although software servers can run on a variety of hardwares. Since servers are usually accessed over a network, many run unattended without
1225-469: The time of the test system is compared to the reference time, and a ratio is computed. That ratio becomes the SPEC INT score for that test. (This differs from the rating in SPECINT2000, which multiplies the ratio by 100.) As an example for SPECint2006, consider a processor which can run 400.perlbench in 2000 seconds. The time it takes the reference machine to run the benchmark is 9770 seconds. Thus
#560439