Tversity updates

aruff 2015-02-17 15:41:32 UTC #1

Hello,
As I mentioned before I have large libraries.
500.000 music titles, more than 500.00 images.
Every time you offer a update this will cause me a personal shock.

Any Update asked again and again what folders where attached, also if I Have Flicker and so on.
There are not to much configurations but except the libraries all other configs where lost (IP, automatic start…).
Because of my large libraries it will use every update more than 3 days to create the new index. (i7, 2600k, SSD for Tversity and Raid for the libraries). mediaserver.exe uses 4-5% CPU Power, not more.

Please could you save the config information within the update prozess, so that we can have a silent update?
Do you need indeed every update the lizenz key, online verified?
Can you increase index speed?
If there are no changes to the database by update, please can you prevent the library refresh in that case?

ronenmiz 2015-02-17 16:33:59 UTC #2

Most updates do not change the database and also do not change the config file format. In those cases, you could back-up the content of db subfolder and of config.xml, then do the update. Then stop the server (it ill start indexing but it is safe to stop it), then restore the old config.xml and db folder and then start it again.

Please note that we advertise support for up to 100,000 items, and while we fully expect 1,000,000 to work we do not test such library sizes on regular basis. I am curious if your huge library even works with other servers.. can you share your experience?

aruff 2015-02-17 16:55:20 UTC #3

Thank you for your advice.
But, all what you write is, from my Point of view, exactly the process that the installation Routine must do. Why must I stop the Server, make a backup and restore it after the update?

I think this is the difference between “full installation” and “update”.
In the case of an update the installation routine must do this for me.

A silent routine as provided by a million programmers.

ronenmiz 2015-02-17 17:28:07 UTC #4

The reason we re-index the content is that there may be changes in the new version that affect indexing. For that reason we chose to always re-index. Given that our indexing is very fast this is not an issue. You have to understand that you are the exception, most people have at most few tens of thousands items and so for them it is very fast..