Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
General Unix Finally something really interesting to talk about. If you've used UNIX or any of its derivatives, you've probably wondered why there's /bin, /sbin, /usr/bin, /usr/sbin in the file system. You may even have a rationalisation for the existence of each and every one of these directories. The thing is, though - all these rationalisations were thought up after these directories were created. As it turns out, the real reasoning is pretty damn straightforward.
Permalink for comment 505841
To read all comments associated with this story, please click here.
JPollard
Member since:
2011-12-31

"As an array of frames, and each frame being an array of pixels."

Um.. video isn't like that. You CAN tread video that way, but it is too incomplete. For instance, a video frame is actually a collection of blocks, each block is compressed. Subsequent blocks use tables generated from the first block for further decoding...

And then there is audio... each audio track associated with a frame is blocked.. and there can be many separate audio tracks.. And for any video track, there can be multiple alternate video tracks.

Now we get to the additional packaging... The video may be encrypted as well... Some tracks encrypted, some not.

NOT GOOD FOR A DATABASE.

And trying to coerce hundreds of different formats into a database would make the database useless. Especially when most data won't need the complexity.

I have worked with wether simulation data. A single run is 100GB or more (one week at low resolution). Some simulations are in 3D for just a few hours (also 100GB). Searches are made for intersections...(weather patterns)... yet the pattern is not something that can be described in SQL, which is really really bad at it.

These searches are closer to what is used in gaming - A 3D mathematical intersection from different points of view....

Database queries are just really stupid at that. And really really slow.

Reply Parent Score: 1