Yes, 17.11 is quite old and it's hard to say what the problem could be. A couple of things I'd look at:
1. Run: `kill -3 go-server-process-id` and it will show you stack traces, which might tell you what the main thread is doing. 2. The pipeline timeline update query is quite time consuming, but everything else being the same, it should be as fast as the older setup. Maybe some DB indexes are missing? 3. You could see if the same behaviour is seen if you move to a new DB schema on the old DB server itself to remove any suspicion on the new DB server's performance. > I notice a lot of the backup and restore docs speak about backup and > restoring the db but it isn't clear whether there is any data that would stop > you loading that dump up in a different location or not - something specific > to the 'old home' of the db data that you'd need to amend before you could > use that as the database for a newer system. I don't think there is anything like that. Cheers, Aravind -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/m28s6ogn44.fsf%40arvindsv.com.
