INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: urlwolf on September 01, 2004, 02:25:50 pm
-
Hi,
It seems to me that MC10 switches views (from audio to images) faster than MC11. Mind you, it's not a small difference. WIth a library of 1200 images and 30000 music files, it takes about 500 msec in MC10, and maybe 3 secs. in MC11.
The difference is the same when comparing search times.
These are rough estimations. I'm testing 11.0.64 vs. 10.0.157.
Do I have something wrong in my config of MC11? Or is that roughly what everyone gets? Is this the cost of the added flexibility for the relational database?
I know that MC11 is more memory efficient. I'm not sure if this lack of snappyness compared with MC10 is worth it, though.
Thanks
-
Make sure you're comparing apples-to-apples. (same view scheme, list style, library size, etc.)
The new DB caching layer should make Media Library views much faster.
If switching to an empty Playing Now is slow, then the slowness is due to the new layout engine. It hasn't been optimized yet, so will speed up with time.
Thanks.
-
Well, I'm using the same library.
-
Is switching to an empty playlist or empty Playing Now view just as slow? (trying to isolate library vs. GUI layout issues)
-
matt, I think it's UI.
Going to the standard homepage (default) is slow too.
-
I'm confused on how MC11 can use MC10's DB and get better speed (other than code optimizations). I have never heard "relational" and MC10 mentioned in the same breath (so it must be Flat File). Flat Files have a different structure than true relational DB's (which have smaller, more numerous tables and indexes). Most of the speed increase comes from eliminating duplicates (which decreases overall DB size), so instead of having 50 Led Zeppelin entries in the Artist table, you just have 1 with an associated index number. Since you have many more indexes from many more tables to keep track of, you'll lose some speed (but more than offset by elimination of redundant data). Am I looking at this correctly Matt?
10-27
-
MC 11 converts an MC 10 database on the first load.
After that, it uses the new data holding system that incorporates data pooling, data compression, and several other enhancements.
You're right that it's always important to consider if the overhead of each "relation" justifies the existence of such a relation. As an example, a simple 4-byte number describing something about the data in each data item would take about 25 MB of memory with King Sparta's library.
The buzz about using a "relational database" on Interact is mostly misguided. MC uses a system highly-tuned for storing the kind of data that's thrown at it. That same system would allow relational artist and album tables, but this isn't something we think makes sense in the UI for most users.
-
Is this the reason renaming files are very slow compared to v10?
Right now, looking at 2-3secs per file with a large database compared to a small one (almost instant) in v11 using the same files.
-
Is this the reason renaming files are very slow compared to v10?
Right now, looking at 2-3secs per file with a large database compared to a small one (almost instant) in v11 using the same files.
We'll fix this in a coming build.
-
Thanks Matt. It's now super fast.