Hello Anouar, \[Adding the group since it might be useful to others\]
> Do you have any suggestions to reduce the size of the database, we have more > than 600 popelines to delete because they are inactive and we dont want to > delete them and keep their data in our database. The database is H2, the .db > file is loaded in memory when starting GoCD and it’s causing a lot of > slowness because the file became voluminous. > > What is the best practice to perform this clean up? > > Migrating to 20.7 to take advantage of postgres is not an option for us > because the validation of the tool after the migration will be costly and > will take too much time and resources, and this validation is mondatory > because we work in -redacted-by-aravind- field. Unfortunately there isn't a known way to delete pipeline history from the database. This was brought up in an early GoCD issue, [issue \#13](https://github.com/gocd/gocd/issues/13). There can be side effects on VSM, fan-in and other parts of GoCD by having "holes" in history. I'd usually recommend moving to Postgres, but you say that's not possible. Given that validation is important, I don't see how deleting random content from the internal database can keep your existing validation … valid. That seems way more dangerous than using a documented database option (Postgres) which offers much better overall performance for the system. The other option when slowness comes up in any system, I guess, is to see if increasing memory and CPU provided, or improving the speed of disk etc. will help. But, that's something that depends on your environment and setup. Regards, 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/m2ft6pxe3f.fsf%40arvindsv.com.
