Improve efficiency of writing MessageHistory as bytes #851
Assignees
Comments
peter-lawrey
added a commit
that referenced
this issue
Mar 14, 2024
peter-lawrey
added a commit
that referenced
this issue
Mar 14, 2024
peter-lawrey
added a commit
that referenced
this issue
Mar 15, 2024
peter-lawrey
added a commit
that referenced
this issue
Apr 12, 2024
…g MessageHistory as bytes #851 (#856) * Make history.as.bytes true by default to improve efficiency of writing MessageHistory as bytes #851 * Added support for copyTo of Message History in bytes format * Added support for copyTo of Message History in bytes format * Added support for copyTo of Message History in bytes format * Code tidy * Use a resource pool * Add a special HISTORY_MESSAGE BacketType instead of reusing UNKNOWN * Remove commented code * Deprecate BYTES_MARSHALLABLE * Added a comment * Fix merge problem
peter-lawrey
added a commit
that referenced
this issue
Apr 12, 2024
…g MessageHistory as bytes #851 (#856) * Make history.as.bytes true by default to improve efficiency of writing MessageHistory as bytes #851 * Added support for copyTo of Message History in bytes format * Added support for copyTo of Message History in bytes format * Added support for copyTo of Message History in bytes format * Code tidy * Use a resource pool * Add a special HISTORY_MESSAGE BacketType instead of reusing UNKNOWN * Remove commented code * Deprecate BYTES_MARSHALLABLE * Added a comment * Fix merge problem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, VanillaMessageHistory uses marshalling code via Bytes; however, it's faster to use raw memory access when direct memory is available.
The text was updated successfully, but these errors were encountered: