2 ms·
Proxying all image decoding to a separate process-per-image isn't likely to be practical anytime soon. Browsers already struggle with too many processes even wi
by pcwalton 11y ago
Proxying all image decoding to a separate process-per-image isn't likely to be practical anytime soon. Browsers already struggle with too many processes even with process-per-tab.
- pbiggar 11y agoI think we live in different worlds. It seems all your examples are downloadable software. I live in a cloudy/SaaS/distributed systems world.
- ajross 11y agoIt's not so crazy. Proxying all video decode to a separate process is, in fact, the deployed architecture on the most popular mobile OS in the world. Sure, there are performance implications. So you come up with complicated meta-streaming APIs to put as much of the intelligence into that "mediaserver" as possible. And on the other side you come up with complicated buffer sharing architectures and APIs to make sure that the output can go straight to the screen instead of back through the app. Oh, and there are (cough) "security" concerns too (which is the whole point to doing this all in a system process), so you need to drill those bits down not just through the userspace but into the driver and out through the HDCP pipeline nonsense below the kernel (which of course needs userspace helpers in most architectures, so up it all comes again through different drill holes...). Er, rather, it is crazy, but for different reasons than you posit. You could totally make it run fast if you had to.
- pcwalton 11y agoSure, but by and large there aren't pages with 1,000 videos on them. There are, however, pages with 1,000 images on them.
- ajross 11y agoYou seriously think that if it were driven by DRM mania, they wouldn't have stuffed a DOM parser into a system server? Again, I'm not saying it isn't crazy, just that it's possible, and that equivalent insanity is already afoot.