Originally posted by bsobel
View Post
Your edit makes me have a ohhhhhh!!!!! wave here!
On Windows I had a growing irriration myself for a few years already. The startup of HomeSeer was more or less random in duration. At certain times I had to wait for 15 minutes before HS3 would finish initialising plugins. Sometimes plugins would timeout even before it would start. At other times it would take a minute or two, but HS would start at reasonable speed.
So almost three weeks ago I got hit by the name change of Philips and my lights started to be not controllable(how conveniant at 10:15 PM of course.....). The issue that is now solved in the beta....
But I was analysing what really happend and wanted to have a clean start of HS. But after half an hour, HS did not start, rebooted the machine, kicked it and shook it, but HS would just stick at initialising and time outing plugins. Pulled my hair there...
So I moved all files to another computer and again tried to restart it, with the same results - it just would not start. On this second pc I checked for large files and found one above 1 GB... a log file, removed it and as expected without result. The second large file was my energy database. It holds 5 years of energy usage.I had to clean the database myself as HST leaves all 0 value rows in it, even with compacting. Did add some other compaction actions in it to make the database even smaller.
Anyway, I removed the database and restarted HS. Within 10 seconds HS started!! This was on the second much more powerfull PC
Of course did the same action on the production PC - removed the energy database and started Homeseer - fast, within 30 seconds all is buzzing again!
I restored the energy database after creating a history table that is holding compacted data to one line per day/device from two months back and longer ago. The database is now reduced from 200Mb to 33 Mb and HS still starts fast. AND I still have my history
I had contact with rjh in the past on this issue, but Rich could not copy the issue and to be honest I did let it rest as I saw not many complaints on the startup time, hoping that in a future release the issue would dissapear. Was planning to mail him, but waited as I wanted to be sure adjusting the Energy db was lasting.
For you it might be very interesting to test removing the energy database? How large is your energy database?
Wim
Comment