In computer architecture, shared graphics memory refers to a design where the graphics chip does not have its own dedicated memory, and instead shares the main system RAM with the CPU and other components. The disadvantage of this design is lower performance because system RAM usually runs slower than dedicated graphics RAM, and there is more contention as the memory bus has to be shared with the rest of the system. It may also cause performance issues with the rest of the system if it is not designed with the fact in mind that some RAM will be 'taken away' by graphics.
| Attributes | Values |
|---|
| rdfs:label
| - Shared graphics memory (en)
- 共享顯存 (zh)
|
| rdfs:comment
| - 在计算机体系结构中，共享显存是指显示卡没有自己的专用内存，而是与中央处理器和其他電腦零件共享随机存取存储器的內存容量。许多核心顯卡就是採用共享顯存这种设计，以降低主板的成本和复杂度，因此此時主板上不需要额外的内存芯片。 通常人們可以通过BIOS来設置共享顯存的容量。不過这样做的一个副作用是，当随机存取存储器的一些內存容量分配给显示卡时，這些被分配的內存就不能被顯示卡以外的電腦零件使用。例如一個內存容量為512字节的计算机，有64字節內存分配給顯示卡，實際上操作系统和用戶可用的內存只有448字节。 (zh)
- In computer architecture, shared graphics memory refers to a design where the graphics chip does not have its own dedicated memory, and instead shares the main system RAM with the CPU and other components. The disadvantage of this design is lower performance because system RAM usually runs slower than dedicated graphics RAM, and there is more contention as the memory bus has to be shared with the rest of the system. It may also cause performance issues with the rest of the system if it is not designed with the fact in mind that some RAM will be 'taken away' by graphics. (en)
|
| dcterms:subject
| |
| Wikipage page ID
| |
| Wikipage revision ID
| |
| Link from a Wikipage to another Wikipage
| |
| Link from a Wikipage to an external page
| |
| sameAs
| |
| dbp:wikiPageUsesTemplate
| |
| Link from a Wikipa... related subject.
| |
| has abstract
| - In computer architecture, shared graphics memory refers to a design where the graphics chip does not have its own dedicated memory, and instead shares the main system RAM with the CPU and other components. This design is used with many integrated graphics solutions to reduce the cost and complexity of the motherboard design, as no additional memory chips are required on the board. There is usually some mechanism (via the BIOS or a jumper setting) to select the amount of system memory to use for graphics, which means that the graphics system can be tailored to only use as much RAM as is actually required, leaving the rest free for applications. A side effect of this is that when some RAM is allocated for graphics, it becomes effectively unavailable for anything else, so an example computer with 512 MiB RAM set up with 64 MiB graphics RAM will appear to the operating system and user to only have 448 MiB RAM installed. The disadvantage of this design is lower performance because system RAM usually runs slower than dedicated graphics RAM, and there is more contention as the memory bus has to be shared with the rest of the system. It may also cause performance issues with the rest of the system if it is not designed with the fact in mind that some RAM will be 'taken away' by graphics. A similar approach that gave similar results is the boost up of graphics used in some SGi computers, most notably the O2/O2+. The memory in these machines is simply one fast pool (2.1 GB per second in 1996) shared between system and graphics. Sharing is performed on demand, including pointer redirection communication between main system and graphics subsystem. This is called Unified Memory Architecture (UMA). (en)
- 在计算机体系结构中，共享显存是指显示卡没有自己的专用内存，而是与中央处理器和其他電腦零件共享随机存取存储器的內存容量。许多核心顯卡就是採用共享顯存这种设计，以降低主板的成本和复杂度，因此此時主板上不需要额外的内存芯片。 通常人們可以通过BIOS来設置共享顯存的容量。不過这样做的一个副作用是，当随机存取存储器的一些內存容量分配给显示卡时，這些被分配的內存就不能被顯示卡以外的電腦零件使用。例如一個內存容量為512字节的计算机，有64字節內存分配給顯示卡，實際上操作系统和用戶可用的內存只有448字节。 (zh)
|
| prov:wasDerivedFrom
| |
| page length (characters) of wiki page
| |
| foaf:isPrimaryTopicOf
| |
| is Link from a Wikipage to another Wikipage
of | |
| is Wikipage redirect
of | |
| is foaf:primaryTopic
of | |
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)