You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported by Hugo Larson on Firebird-java, when using Jaybird 3 in a (large) application compiled with Excelsior Jet, the initialization of the default EncodingFactory can take a long time if not all character sets are included in the compiled application (about 500ms per missing character set).
I have not been able to reproduce this behavior in Java applications running in a 'normal' JVM, but it might be worthwhile to change the character set handling to initialize on first use of a character set (if possible).
Note that including the missing character sets in the compiled Excelsior Jet application makes it fast again.
Submitted by: @mrotteveel
As reported by Hugo Larson on Firebird-java, when using Jaybird 3 in a (large) application compiled with Excelsior Jet, the initialization of the default EncodingFactory can take a long time if not all character sets are included in the compiled application (about 500ms per missing character set).
I have not been able to reproduce this behavior in Java applications running in a 'normal' JVM, but it might be worthwhile to change the character set handling to initialize on first use of a character set (if possible).
Note that including the missing character sets in the compiled Excelsior Jet application makes it fast again.
Commits: 5463983 08bdfd3 70be7eb
The text was updated successfully, but these errors were encountered: