I’m sorry, but it makes no sense that performance was always fine, even with much slower CPU’s (per core speed) and all of a sudden it’s unusable. This isn’t a new install. This has been running fine on this setup. There is a culprit here, and it’s not the specs of the hardware.
what I am saying, is the recent beta releases have had database changes, which CAN tank a LONG time to complete, depending on your database size, cpu/disk speed. 5-30 minutes is not unheard of.
if you did not wait for the database migrations complete it could be possible the database got corrupted. you can try to restore a recent database from the database backups folder or your own backups if you made them.
if pms is starting up fine but performance is slow, you can try rolling back to an older version of pms (database changes will usually roll back and take about the same amount of time to process).
It’s not the database migration or database corruption. I’ve run the Db consistency check utility and it’s fine. The performance issue and constant rescanning happens after the “database migration”. I’m monitoring the logs constantly to see if there are any clues.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
