Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
*Notices that SMPlayer takes a lot of the iGPU and CPU*
*Relaunches SMPlayer to use dedicated Nvidia GPU*
> I don't really want to play videos anymore when running on this card.
> MPlayer crashed by bad usage of CPU/FPU/RAM.
(that last one is an actual log btw)
Alright, got it. I bought this fucking PC just for its fucking "powerful" GPU. It already locked me into using WanBLowS on that piece of garbage. Yet now that NvuDiA piece of garbage is gonna act worse than a fucking paperweight?! Seriously?!!
FUCK YOU NVIDIA!!! Linus Torvalds called your shitty cards shit on Linux.. I call it shit on every fucking OS out there!!! MOTHERFUCKERS!!!3 -
So recently I had an argument with gamers on memory required in a graphics card. The guy suggested 8GB model of.. idk I forgot the model of GPU already, some Nvidia crap.
I argued on that, well why does memory size matter so much? I know that it takes bandwidth to generate and store a frame, and I know how much size and bandwidth that is. It's a fairly simple calculation - you take your horizontal and vertical resolution (e.g. 2560x1080 which I'll go with for the rest of the rant) times the amount of subpixels (so red, green and blue) times the amount of bit depth (i.e. the amount of values you can set the subpixel/color brightness to, usually 8 bits i.e. 0-255).
The calculation would thus look like this.
2560*1080*3*8 = the resulting size in bits. You can omit the last 8 to get the size in bytes, but only for an 8-bit display.
The resulting number you get is exactly 8100 KiB or roughly 8MB to store a frame. There is no more to storing a frame than that. Your GPU renders the frame (might need some memory for that but not 1000x the amount of the frame itself, that's ridiculous), stores it into a memory area known as a framebuffer, for the display to eventually actually take it to put it on the screen.
Assuming that the refresh rate for the display is 60Hz, and that you didn't overbuild your graphics card to display a bazillion lost frames for that, you need to display 60 frames a second at 8MB each. Now that is significant. You need 8x60MB/s for that, which is 480MB/s. For higher framerate (that's hopefully coupled with a display capable of driving that) you need higher bandwidth, and for higher resolution and/or higher bit depth, you'd need more memory to fit your frame. But it's not a lot, certainly not 8GB of video memory.
Question time for gamers: suppose you run your fancy game from an iGPU in a laptop or whatever, with 8GB of memory in that system you're resorting to running off the filthy iGPU from. Are you actually using all that shared general-purpose RAM for frames and "there's more to it" juicy game data? Where does the rest of the operating system's memory fit in such a case? Ahhh.. yeah it doesn't. The iGPU magically doesn't use all that 8GB memory you've just told me that the dGPU totally needs.
I compared it to displaying regular frames, yes. After all that's what a game mostly is, a lot of potentially rapidly changing frames. I took the entire bandwidth and size of any unique frame into account, whereas the display of regular system tasks *could* potentially get away with less, since most of the frame is unchanging most of the time. I did not make that assumption. And rapidly changing frames is also why the bitrate on e.g. screen recordings matters so much. Lower bitrate means that you will be compromising quality in rapidly changing scenes. I've been bit by that before. For those cases it's better to have a huge source file recorded at a bitrate that allows for all these rapidly changing frames, then reduce the final size in post-processing.
I've even proven that driving a 2560x1080 display doesn't take oodles of memory because I actually set the timings for such a display in order for a Raspberry Pi to be able to drive it at that resolution. Conveniently the memory split for the overall system and the GPU respectively is also tunable, and the total shared memory is a relatively meager 1GB. I used to set it at 256MB because just like the aforementioned gamers, I thought that a display would require that much memory. After running into issues that were driver-related (seems like the VideoCore driver in Raspbian buster is kinda fuckulated atm, while it works fine in stretch) I ended up tweaking that a bit, to see what ended up working. 64MB memory to drive a 2560x1080 display? You got it! Because a single frame is only 8MB in size, and 64MB of video memory can easily fit that and a few spares just in case.
I must've sucked all that data out of my ass though, I've only seen people build GPU's out of discrete components and went down to the realms of manually setting display timings.
Interesting build log / documentary style video on building a GPU on your own: https://youtube.com/watch/...
Have fun!20 -
I need new mobile hardware because my old netbook from 2010 just doesn't cut it anymore.
I've ordered this fellow here: https://tuxedocomputers.com/en/...
AMD 4700U (TDP 15 W), iGPU only, 2x16 GB 3200 RAM, 2 TB Evo 860. Delivery in November because APU-only laptops are totally hot RN.
Maybe I can install Mint on that if I go for a 5.8 mainline kernel. At least it has Intel wifi, not Broadcom.12 -
!rant/story:
Aaayoo issya boi the OG rapper straight outta Compton, wassup?!
Nah, for real, though.: How are y'all doing? It has been a long time. I hope y'all are having a great time (can sense some peoples' incoming negative comments due to corona).
I built my completely new first gaming rig like a few weeks ago after my school laptop stopped showing any signals.
The specifications are the following.:
- Mobo: MSI B450 TOMAHAWK MAX
- CPU: AMD Ryzen 5 3600 (no iGPU)
- dGPU: KFA2 RTX 2070 SUPER OC
- 2nd dGPU: GTX 550 TI (this one gets a new rant/post)
- RAM: 2x G.SKILL Ripjaws V 8 GB 3600 MHz
- PSU: Be quiet 650 W (It was the platinum edition afaik. I originally bought the 600 Watt Gold edition, but somehow they sent me the 650 Watt for no additional charge... which is great for me haha)
- HDD: 2x 4TB NAS HDD in RAID1 configuration (to load all of my games around 2 TB right now. Got the two HDDs for 110 Euro including the SATA Data cables)
- SSD: One Intenso 240 GB SSD and a reused Samsung 256 GB SSD from my old broken Lenovo laptop
- Case: Be quiet Pure Base 500 black with a glass panel on the side
While building my first PC, it was one hell of a challenge. I knew how it all was working in theory, but to put it all together, practically, was a bit of a challenge, but it was a nice challenge. I learned a lot and have a performance gain I could only ever dream of.
I used to play my games first on a Toshiba satellite l750d laptop (around 40 fps in cs:go with the lowest gfx settings) and then on a Lenovo e51-80 laptop (around 30 fps max minecraft with no shaders and texture packs).
Now I play cs:go on Kubuntu with 400 fps at peak with ultra high graphics. It is unbelievable.
I couldn't trust the system when I turned on the fps display the first time I saw it.
6 -
Would you get a new laptop with Intel Celeron N3450, or slightly older with Intel Core i5 4310U? I'm talking both having 256 GB SSD, 8GB RAM and only iGPU? Both for pretty much same price.9
-
So few days ago I've installed Mojave from clean setup (Hackintohsh) and works smooth as butter, and today I woke up in the morning and sat down to work, my pc was running on windows so I restarted it, there was some updates to be installed but what a heal will install them later, so the pc started booting in Mojave, usually takes few seconds but this time it got stuck on the loading screen, so rebooted again and this time added -v boot parameter to clover to see whats going on, got some errors about IGPU (had to use intel's gpu.. thanks Nvidia .!.), did few googling some suggested using -disablegfxfirmware but that didn't work, so rebooted again.. hoping I would get more info, guess what? windows 10 was in hibernation (possibly because there were updates to be installed on boot) and that somehow prevented mojave from using the ssd i guess? not sure exactly, so In the end I got very lucky cause if I didn't read the message I would have reinstalled the mojave and loose a day at work... politely f*** you windows updates!
Top Tags
Weekly Rant
View