Separate stanza parsing from database loading #373
Comments
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Feb 16, 2024
By not parsing database content immediately, this parsing can be done after the database connection has been released. This should reduce resource contention.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Nov 22, 2024
By not parsing database content immediately, this parsing can be done after the database connection has been released. This should reduce resource contention.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Nov 22, 2024
By not parsing database content immediately, this parsing can be done after the database connection has been released. This should reduce resource contention.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The constructor of ArchivedMessage attempts to parse a stanza. This can be a resource-intensive operation.
ArchivedMessage instances are typically created in bulk while iterating over database content.
The resource-intensive stanza parsing should not prevent the database resources from being released, as this keeps those resources from being available for other database operations.
To improve performance, modify the code in such a way that the optional stanza that is part of a message is not parsed in the constructor.
The text was updated successfully, but these errors were encountered: