[high5ths]

New version seems faster in some respects, but at least ridiculously slow in another: searching with the Column Browser open.

I have a huge library--~63000 songs; I'm a musician--and although iTunes 10.7 search was quite reasonable, the new iTunes takes several seconds to do anything after typing a query. Even if I turn off "Search Entire Library" (so that it only searches the active screen, like Music) it is incredibly unresponsive. I'm talking ~6 seconds for the UI to update and the program to become responsive again. If I limit the search to only one field (e.g., Composer) it is faster, but still substantially slower than iTunes 10.7 (~2 seconds for the UI to update, compared to the previous results of nearly instant), and it makes the search much less useful.

Closing the Column Browser speeds up filtering, though it's still slower than 10.7.

[dbrannan]

Perhaps iTunes 11 needs to index your library over again before the speed improves?

[high5ths]

Possibly... though Activity Monitor (or top) doesn't show anything suspicious. If I stop audio from playing, iTunes drops to about 4% CPU. (And mdworker doesn't appear to be working overtime either.) With the Column Browser open, searching in iTunes causes a leap to 100% CPU until the UI updates. Column Browser closed, searching causes a momentary leap, but not to 100%, and obviously it's over very quickly.

There's clearly something up with the coding of the Column Browser.

[zerovox]

I doubt it, it seems to be using the same plist format(essentially, a glorified xml file) as previous versions.

[hokkos]

the plist is only for external app, internally it uses a sqlite.