NVIDIA Blackwell 50xx

 idu vam opet podaci potrebni za grafički prikaz koji grafa renderira, uhvatili se tih  parsto mb ko utopljenik za slamu, a drugo? ništa?

od gigabajta i gigabajta prostora za os, engine i drajvere o kojima lupetaš, spao si na tu rezervaciju od parsto mb kao glavni argument 

što je s ostatkom priče? spala knjiga na tri slova 

dečeci, educirajte se, bar to ne košta ništa

 što si točno ti profesore pokazao od znanja? da se znaš služiti ad hominemom, bravo baš profesorski

ostalo ništa jel? ah da, podsjetio si da os rezervira parsto mb vrama, kao argument da nejde samo ono što je potrebno za grafiku

a što ide u tih parto mb? prikaz desktopa, taskbara i drugih grafičkih elemenata os-a inače renderira psu a ne grafa, jel?

e moj profesore

EDIT

pa pokaži onda znanje kojim se busaš, što je netočno?

- lupetate o drajverima, osu i game engine koji idu u vram - netočno, oni ferceraju u ramu, ne vramu

- lupate da monitoring app vidi sve - ne vidi ono što se događa na razini game engine i pogotovo ne u drajverima i alatima nevidije i amd-a

monitoring app se oslanja na os, koji je površinski layer, sve ispod ne vidi

- jel netočno da se igra pruži preko veće količine vrama ako ga ima više kao kod 5090, a da može bez problema raditi i s manje zauzeća

odgovori bar na nešto, sve što si rekao je ad hominem i apasolutno ništa drugo, osim tih parsto mb kojih si se uhvatio ko pijan plota, a za koje očito nemaš pojam zašto su zauzete u vramu od strane os

EDIT 2

reagirao sam na koleginu tvrdnju da njemu njegov monitoring alat pokazuje potrošnju, a da to znači da grafa traži toliko i toliko vrama

njegov alat, za koji je sam rekao da se veže uz os, što nikako ne znači da su ti podaci apsolutno točni i još manje da taj podatak u monitoringu znači da toliko igrica nužno treba (u suprotnom bi s manje vrama došlo do gličeva zar ne? što ofkors nije istina jer je poznato da se ponekad igre pruže i preko više vrama nego im nužno treba - zato jer time olakšavaju pritisak na procesor, jer sve što drajveri rade da hendlaju vram udara na proc - otud i cpu driver overhead

nisam ništa rekao za alate koje koristi industrija, jer postoje i drukčiji alati od onih koje koriste kućni korisnici, a dosta ovisi i koliko će developeri dopustiti da se vidi - za to sam dao i link na objašnjenje i citat nevidije: 

Do On Screen Display (OSD) Tools Report VRAM Usage Accurately?

Gamers often cite the “VRAM usage” metric in On Screen Display performance measurement tools. But this number isn’t entirely accurate, as all games and game engines work differently.

In the majority of cases, a game will allocate VRAM for itself, saying to your system, ‘I want it in case I need it’. But just because it’s holding the VRAM, doesn’t mean it actually needs all of it. In fact, games will often request more memory if it’s available.

Due to the way memory works, it’s impossible to know precisely what’s being actively used unless you’re the game’s developer with access to development tools. Some games offer a guide in the options menu, but even that isn’t always accurate.

evo profesore, kad ti je teško guglat... ai odgovor, on to bolje sroči od mene 

A game engine uses a layered architecture to manage interactions with the operating system (OS), device drivers, and developer tools. The OS and drivers form the lowest layers, providing the foundational services that the engine's platform-independent layers rely on for hardware access (like graphics, input, and audio). The engine's own higher layers build on this by providing standardized APIs for things like rendering, physics, and audio, allowing developers to focus on game logic rather than low-level hardware details. 
How layers work together
Drivers and OS Layer: This is the foundation. The OS provides core services, and specific device drivers translate the engine's generic commands into instructions for hardware like a graphics card, sound card, keyboard, or mouse. For example, a driver for a graphics card tells it how to render triangles and apply textures.
Platform Independence Layer: The engine builds a layer on top of the OS and drivers to abstract away differences between platforms (Windows, macOS, Linux, consoles). This layer handles tasks like file I/O, networking, and other low-level operations in a consistent way, so the code written for one platform can run on another.
 

Core Systems and Subsystems Layer: This is where the engine provides its core functionalities, such as the rendering engine, physics engine, audio system, and animation engine. These are complex systems that depend on the platform independence layer and, indirectly, the OS and drivers below them.
Game Framework and Tools Layer: This is the highest level, where game-specific subsystems and developer tools reside.
Game-specific subsystems: These are the parts of the engine developers use to build their game, like the GameFramework classes in Unreal Engine that manage player controllers and game modes.
Tools: This includes the editor and other utilities used during development. These tools use the same runtime components as the game itself, but also provide extra features for asset management, debugging, and level editing.

 Viš da ljudi koji plaćaju pretplatu imaju VIP tretman