Consider using "php artisan schema:dump"

After running the php artisan migrate command, which executes database migrations, the database schema is effectively updated to reflect the changes defined in those migrations. However, as your Laravel application grows and accumulates migrations over time, executing migrations can become time-consuming, especially if there are a large number of them.

In such scenarios, relying solely on migrations to update the database schema might not be the most efficient approach, particularly during development or testing phases where frequent schema changes are made. This is where php artisan schema:dump comes into play as a valuable tool.

By using php artisan schema:dump after running migrations, developers can quickly generate a snapshot of the updated database schema. Unlike executing individual migrations, which might involve processing a large number of files and database operations, dumping the schema offers a faster and more streamlined alternative.

Since php artisan schema:dump directly reads the current state of the database schema from the database itself, it bypasses the need to iterate through migrations. As a result, it can provide a near-instantaneous snapshot of the database schema, even when dealing with hundreds of migrations.

In my situation, where I have over 100 migrations, utilizing php artisan schema:dump before running migrations resulted in a significant speed boost, exceeding 85% compared to solely relying on migrations.