This happens pretty frequently, and I don’t know if it’s because I like to have multiple tabs open or if because I have too many horses, but the app frequently hangs and starts timing out. I’m not sure if something is timing out and there’s still backend processing happening or something else. Closing the tab or reloading the page doesn’t help. If I start to get this error, then navigating in both the old and new app are effected.
It’s made the app unusable and to the point where I’m like “Hey, maybe I should really thin the herd.”
It consistently seems to be triggered when I am in the new app. When I am in the old app things stay pretty stable. Could totally be coincidence. So hopefully things will be less sad in the future. I just want to call it out since the new app is where I am experiencing the timeouts.
My hypothesis is that the old database is hogging all the server resources, despite the various settings I have to tell it not to. The new app talks mostly to the new database, but the new database craps out when the old database takes the server hostage. So if we can get both apps talking to one (new) database, hopefully it should be stable.
I’m going to see if I can just spend a day or two migrating the data over, but not worrying about the code, and then we can see how everything behaves with just one database. If nothing else, it’d make moving over to a new (much beefier) server much simpler.
