We are using an ABP application built on .NET Core with Entity Framework Core migrations for database schema management. Over time, the project has accumulated a large number of migration files. We are currently experiencing a performance issue during the build process. Building the project consumes a significant amount of system resources, with CPU utilization frequently reaching 98%, resulting in slow build times and reduced development efficiency. Could you assist in identifying whether the large number of Entity Framework Core migrations could be contributing to this issue? Additionally, I would appreciate recommendations on best practices for managing a large migration history and optimizing build performance without affecting the existing database schema or deployment process.
we are encountering an issue while attempting to log in to ABP Studio. This appears to be critical, as all ABP-related services stop functioning
