dido:public:ra:xapend:xapend.c_hwarch:server:hw
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.c_hwarch:server:hw [2021/06/11 14:39] char |
dido:public:ra:xapend:xapend.c_hwarch:server:hw [2022/01/15 14:48] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== About ===== | ===== About ===== | ||
| - | Hardware [[dido:public:ra:xapend:xapend.a_glossary:s:server | Servers]] can vary widely from personal computers (i.e., [[dido:public:ra:xapend:xapend.c_hwarch:desktop|Desktop Computers]]) to specially built rack mounted computers and depends on the amount of work that needs to be done and the number of [[dido:public:ra:xapend:xapend.a_glossary:c:client | clients]] that need to be supported. For example, quite often database servers are software that can run on a person computer to service the needs of an individual using the machine as a personal computer or can be on many rack mounted servers supporting thousands to millions of clients. As a general rule, Servers are more powerful and expensive than the clients hardware that connect to them. The power of a server is not just measured in the speed of its CPU, but also in its ability to handle events, connections and speed of accessing memory. | + | Hardware [[dido:public:ra:xapend:xapend.a_glossary:s:server | Servers]] can vary widely: from personal computers (i.e., [[dido:public:ra:xapend:xapend.c_hwarch:desktop|Desktop Computers]]) to specially built rack mounted computers depending on the amount of work that needs to be done and the number of [[dido:public:ra:xapend:xapend.a_glossary:c:client | clients]] that need to be supported. For example, quite often database servers are software that can run on a personal computer to service the needs of an individual using that machine or can be on many rack mounted servers supporting thousands to millions of clients. As a general rule, Servers are more powerful and expensive than the client's hardware connected to them. The power of a server is not just measured by the speed of its CPU, but also in its ability to handle multiple events and connections and its memory access speed. |
| - | Many servers, whether running locally on a personal computer or remotely on large clusters of servers, are accessed over a network usually the [[dido:public:ra:xapend:xapend.a_glossary:e:ethernet]]. They are intended to run unattended without [[dido:public:ra:xapend:xapend.a_glossary:h:hmi]] or [[dido:public:ra:xapend:xapend.a_glossary:g:gui]]. These servers are configured and managed remotely using software specifically designed for that purpose. Often the management is done using web based interfaces accessible using browsers and secure connections and [[dido:public:ra:xapend:xapend.b_stds:tech:ieee:posix | POSIX]] compliant interfaces. | + | Many servers, whether running locally on a personal computer or remotely on large clusters of servers, are accessed over a network -- usually the [[dido:public:ra:xapend:xapend.a_glossary:e:ethernet]]. They are intended to run unattended without [[dido:public:ra:xapend:xapend.a_glossary:h:hmi]] or [[dido:public:ra:xapend:xapend.a_glossary:g:gui]]. These servers are configured and managed remotely using software specifically designed for that purpose. They are typically managed using web based interfaces accessible via browsers over secure connections and [[dido:public:ra:xapend:xapend.b_stds:tech:ieee:1003.1| POSIX]] compliant interfaces. |
| - | Historically, Servers used [[dido:public:ra:xapend:xapend.a_glossary:c:cpu]] that were either the [[dido:public:ra:xapend:xapend.a_glossary:c:cisc]] or [[dido:public:ra:xapend:xapend.a_glossary:r:risc]] architectures. While the [[dido:public:ra:xapend:xapend.a_glossary:c:cpu | Central Processing Units (CPUs)]] are designed to quickly handle a wide-range of general tasks sequentially, they are not well suited for many small tasks that can be handled in parallel. Recently some servers are built using [[dido:public:ra:xapend:xapend.a_glossary:g:gpgpu | General-Purpose Graphics Processing Units (GPGPUs)]] instead of CPUs. These Servers are not processing lots of graphics and images as implied in the name GPGPU, but because the GPGPU excels at performing lots of small tasks in parallel (i.e., concurrently). | + | Historically, Servers used [[dido:public:ra:xapend:xapend.a_glossary:c:cpu]] that were either [[dido:public:ra:xapend:xapend.a_glossary:c:cisc]] or [[dido:public:ra:xapend:xapend.a_glossary:r:risc]] architectures. While the [[dido:public:ra:xapend:xapend.a_glossary:c:cpu | Central Processing Units (CPUs)]] are designed to quickly handle a wide-range of general tasks sequentially, they are not well suited to handling many small tasks that in parallel. Recently some servers have been built using [[dido:public:ra:xapend:xapend.a_glossary:g:gpgpu | General-Purpose Graphics Processing Units (GPGPUs)]] instead of CPUs. Despite their name (GPGPU), these Servers are not used to process lots of graphics or images, instead, they are used to perform lots of small tasks in parallel (i.e., concurrently). |
| - | Consequently, GPGPU based servers performing parallel operations on multiple sets of data have been adopted by for non-graphical tasks such as machine learning and scientific computation. Designed with thousands of processor cores running simultaneously, GPGPUs enable massive parallelism with each core performing efficient calculations simultaneously. | + | Consequently, GPGPU based servers performing parallel operations on multiple sets of data are being employed to support non-graphical tasks such as [[dido:public:ra:xapend:xapend.a_glossary:m:machine_learning|machine learning]] and scientific computation. Designed with thousands of [[dido:public:ra:xapend:xapend.a_glossary:p:processor|processor]] cores running simultaneously, GPGPUs enable massive parallelism with each core performing efficient calculations simultaneously. |
| Line 15: | Line 15: | ||
| * **File Servers** are responsible for the central storage and management of data files | * **File Servers** are responsible for the central storage and management of data files | ||
| - | * **Policy Servers** are security components of a policy-based network that provides authorization services and facilitates tracking and control of files | + | * **Policy Servers** are security components of a [[dido:public:ra:xapend:xapend.a_glossary:p:policy|policy]]-based network that provides authorization services and facilitates tracking and control of files |
| * **Print Server** provides access to one or more network-attached printers | * **Print Server** provides access to one or more network-attached printers | ||
| * **Media Server** provides access to streaming video and audio | * **Media Server** provides access to streaming video and audio | ||
| * **Game Server** provides access to the authoritative source of events shared across users in multiplayer video games | * **Game Server** provides access to the authoritative source of events shared across users in multiplayer video games | ||
| * **Domain Servers** provides Internet Domain Name translation to internet addresses | * **Domain Servers** provides Internet Domain Name translation to internet addresses | ||
| + | |||
| ===== DIDO Specifics ===== | ===== DIDO Specifics ===== | ||
| + | |||
| [[dido:public:ra:xapend:xapend.c_hwarch:server:hw | Return to Top]] | [[dido:public:ra:xapend:xapend.c_hwarch:server:hw | Return to Top]] | ||
dido/public/ra/xapend/xapend.c_hwarch/server/hw.1623436780.txt.gz · Last modified: 2021/06/11 14:39 by char
