Choose database engine ?
First of all, I must say that Serviio works great, and that it's really a nice piece of software.
Sorry if I have already posted those thoughs in another thread, but I think it was misplaced.
As I experiment some performance problem with my numerous files on my server, I was asking myself if it can be a benefit to put it on another database engine as Serviio is acceding to the database every X min to check if metadata already exists. It can be very long with numerous files.
I think that one piece of the problem is the java browsing. There's a hope with Java 7 in this direction which is "event oriented", and so Serviio don't have to always browse all files in all directories... but simply ask for a change in it.
The other piece is perhaps the embeded java database engine. I know that embeded database can be very fast as they are load in memory, but there's one moment where the database cannot fit into memory

Don't know really if Derby is faster than MySQL or other db engine, but is it possible to have the connection URL in a propertie file, in order to choose the db.
Also, I already have a MySQL engine running on my linux DLNA server, and it would be nice to put Serviio db in it (only one db engine on the server, less memory usage). I imagine that using Derby is probably a "deployment choice", as it more easier as the database engine is embeded with the server... and I can understand and agreed, but with putting the database URL in a properties file, some of us can easily choose to change the db engine.
As a Java developper, I know that there's a little code change in the Connection Pool class, but the choice is yours of course

Hope I can by heard

Have a nice day.