Songbird performance scalability solution.
Songbird is unusably slow for moderately sized music collection of only ~15,000 songs, which is less than 1/2 of my full collection. iTunes is also very slow for collections this size. Just because iTunes can't do it isn't a valid excuse, Amarok using a MySQL backend rocks a collection of this size with ease. I know when Amarok uses SQLite (the default), its also unusably slow. Perhaps songbird could use MySQL with the innodb engine like Amarok? If there is a Intellectual property issue then PostgreSQL(bsd license) would also be amazing!
Please improve the speed of Songbrid with moderately sized collections so I can use it! Until then I'll be stuck with Amarok+MySQL.
Peace
Please improve the speed of Songbrid with moderately sized collections so I can use it! Until then I'll be stuck with Amarok+MySQL.
Peace
5
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
-
Inappropriate?Hi Michael,
We do not have plans to move from SQLite at this time though we do devote development time in every release to improve performance and stability. Hopefully we'll get flying fast enough for you to give us another try!
I’m thankful
-
Inappropriate?Thanks Laura. I am not asking you to migrate to another database, i am asking you to support more than one database such as Amarok. I know sqlite is the problem and until you can support multiple database no serous audophiles will be able to use your software. If you don't believe me, just try and use it with 15k files, it will be completely unusable. Then try 30 or 50k files... it won't even index them.
-
Inappropriate?Hey Larua, looks like this is a very common problem:
http://getsatisfaction.com/songbird/t...
As long as you force users to use SQLite this problem will NOT go away. -
Inappropriate?Hey Michael,
Trust me, it's not at all about me not believing you, just passing on the info I was able to get confirmed from the team. It is indeed an ongoing issue and hopefully supporting multiple databases is something we can strive for in the future, it's just not on the road map right now.
I’m sorry
Loading Profile...




EMPLOYEE