rvtama.blogg.se

This is yet more downloading and buffering of potentially larger amounts of data for the same amount of video.Īll of this means libraries that do lots of work with lots of elements. YouTube also uses code to check your speed and might start with a lower quality stream and pre-buffer a high quality stream once it can see the connection speed is up to it or vice versa.the webpage is designed to be used on resolutions all the way from 1280*720 up to the newest 4k and 8k resolutions and will either load larger resolution elements or rely on raster images (which equates to yet another format to decode and be able to view - more code and buffers).all of the data you see has to be handled by the browser and processed in some way before handing over to your graphics card.there are several (tens, if not more) pieces of javascript running doing everything from handling mouse events to advertising tracking and more.

the webpage does not fully unload when you navigate within the site, it has a lot of dynamic self management and navigation going on.If your graphics card lacks hardware video decoding for the format selected then the browser must decode the video itself and use a lot more memory. All of these need some program within your browser to play as well as associated buffers to download and pass data to your graphics card. it can have video of several different types in the main area and needs to be able to play hevc, h.264, webm and some others.it has a large area of "suggested" videos, all of which equate to yet another image for the browser to load and show to you.it is highly dynamic, with several large sections of comments (which are expandable and contain sub menus and dynamically appearing "add comment" boxes).YouTube in particular is a pretty demanding webpage.

Playing video and showing a "simple" webpage is not as easy as you think it is.