is HSQL really bad?
Answered
We use 5 active projects with 35 build configurations. We have no problem with performance. Are there reasons to migrate from HSQL on external database? Which?
Please sign in to leave a comment.
Hello Dmytro,
There are two reasons:
1) the HSQLDB engine is prone to crash (e.g. if the TeamCity process is forcefully stopped); unless you keep regular backups, it is fairly hard to restore one and usually leads to the unrecoverable loss of data.
2) the HSQLDB tends to get very slow at around 200-300 MB worth of database file size.
While the (2) can be worked around to an extent by ensuring particularly aggressive cleanup settings and keeping low on projects/configurations, (1) is the main reason usage of external database is recommended; in general, it might be cheaper to use one than to mitigate the risks of losing data because of HSQLDB failure.
I hope this helps; please let me know if there is anything else I could assist with.
Hi Fedor,
Thank you for a quick and detailed answer.
if I stop Docker Container with TeamCity for maintenance work (backup, update and etc), is it forcefully stopped? can it lead to a crash?
Best regards
Dmytro Goncharov
Hello Dmytro,
You are welcome! As far as I could see, in this case TeamCity should be stopped gracefully.