We're updating the issue view to help you get more done. 

Speed optimizations

Description

liquibase.change.ChangeFactory.init() seems to take a lot time during database update process. Would it be possible to register classes lazily in ChangeFactory.create()? That would probably optimize the common case of not having any (or just a few) new change sets to execute.

And is it necessary to analyze all supported and required databases in liquibase.change.AbstractChange.createChangeParameterMetadata()? After all we are just using one database?

Environment

H2, Spring, JDK11, Windows, i5-3550, Visual VM 143

Status

Assignee

Unassigned

Reporter

milanka

Labels

None

Components

Affects versions

3.6.3

Priority

Minor