开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Re: Graphics cards and Monitors for the shack/ DXLab


 

开云体育

Perplexity offers this comment about Graphics card memory and system memory:

?

A graphics card primarily uses its own dedicated memory, known as Video RAM (VRAM), for handling graphics-related tasks such as storing textures, shaders, and rendered images

However, in certain situations, a graphics card can utilize the motherboard's system RAM, but this is not a standard or preferred method for several reasons:

--Integrated Graphics: When a system uses integrated graphics (i.e., graphics processing capabilities built into the CPU or motherboard), it relies on system RAM for graphics processing. This is because integrated graphics do not have their own dedicated VRAM

--Shared Memory: Some systems, particularly those with integrated graphics, allow for a portion of system RAM to be allocated as shared memory for graphics processing. This is more common in laptops or systems without a dedicated graphics card

--PCIe Bandwidth: Modern graphics cards can access system RAM via the PCIe interface, but this is generally slower than using VRAM. The PCIe bus allows for data transfer between the GPU and system memory, but it is not typically used for primary graphics rendering due to bandwidth limitations

--Outsourcing to System RAM: In cases where a GPU runs out of VRAM, it might use system RAM as a fallback, but this is inefficient and can lead to performance drops

?

In summary, while a graphics card can technically use motherboard memory under specific conditions, it primarily relies on its own VRAM for optimal performance.? While a GPU cannot directly use system RAM as a substitute for VRAM, system RAM can be utilized in specific contexts through software management or when using integrated graphics. The performance impact of relying on system RAM for graphics tasks is generally significant due to slower access speeds compared to dedicated VRAM.

------------------------------------------------------------------------------------End of Perplexity quote--------------------------------------------------------------

?

In my shack computer I have an old graphics card with 4 Gig of memory.? That amount of memory is not enough to store the images on my 3440 X 1400, 34” monitor (DXLab + WSJTX improved)? and my 21”, 1920 x 1080monitor (DXAtlas + DXMaps).? So, when my video system goes to sleep, upon wake up, it takes an annoying amount of time to refresh the two screens.?

?

On my house office computer, I have a video card with 16 Gig of video memory.? I have a 27”, 2560 x 1440 monitor (4,816,000 pixels) , on that video system, when awakened from sleep the previous images instantly pops up.? I can’t afford the card that has enough video memory to pop-up that many pixels—nor would I buy the computer case big enough to fit that card.

?

When running DXLab and associated Amateur Radio related software, we have a lot of pixels loaded with useful images and text, the rate of change of those pixels is quite slow in comparison to design tools and gaming.

?

Display pop up time is not a meaningful measure.? But it does show the relative speed of update from video memory vs mother-board memory.

?

73,

Dave, w6de

?

From: [email protected] <[email protected]> On Behalf Of Richard Hill via groups.io
Sent: 27 March, 2025 18:10
To: [email protected]
Subject: Re: [DXLab] Graphics cards and Monitors for the shack/ DXLab

?

Regarding Spot collector hardware needs, I think they relate to the motherboard hardware and not to the graphics card unless the graphics card uses motherboard resources and then a limitation in resources could affect the graphics system and display capabilities (probably on low end systems) when under heavy loads.??

?

Yes?

?

Rich, NU6T

?

On Thu, Mar 27, 2025 at 10:49?AM Dave AA6YQ via <aa6yq=[email protected]> wrote:

+ AA6YQ comments below

is SpotCollector multi-processor or multi-core aware?

+ I did not design SpotCollector or any other DXLab component to detect and exploit the presence of multiple cores. However, testing revealed that SpotCollector's performance does increase if 2 or 3 cores are assigned - likely due to parallelism in the Jet database engine. If you have SpotCollector configured to direct PropView to generate a propagation forecast for each new Spot Database Entry, then assigning PropView to a core would likely also improve performance,?

+ See the Hardware Capabilities section of



? ? ?73,

? ? ? ? ? ? Dave, AA6YQ


?

--

Richard Hill

Join [email protected] to automatically receive all group messages.