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
go get -u github.com/orijtech/structslop/cmd/structslop
structslop github.com/godror/godror
reported a few structs that could be rearranged to become smaller.
I understand that *char and its length should be together, so maybe this rearrangement has too few gains and too big price for structs that are only have a few instances in a program, such as dpiConnCreateParams or dpiCommonCreateParams.
But may more gain more with dpiSubscrMessageTable and dpiSubscrMessage.
The text was updated successfully, but these errors were encountered:
@tgulacsi, thanks for the suggestion. That's something that could only be considered for version 5 when structure changes like these are possible without breaking backwards compatibility. So I'll keep this in mind when version 5 is being prepped.
tgulacsi
added a commit
to godror/godror
that referenced
this issue
Nov 19, 2021
Object creation and release fragments memory. This is not a real memory
leak (less than 3 bytes for 100 iteration with standard malloc, and less
than 1 byte for 100 iteration with jemalloc).
To try with jemalloc:
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.1 go test -run=198 -v
ODPI-C issue: oracle/odpi#149Closes#198
reported a few structs that could be rearranged to become smaller.
I understand that *char and its length should be together, so maybe this rearrangement has too few gains and too big price for structs that are only have a few instances in a program, such as dpiConnCreateParams or dpiCommonCreateParams.
But may more gain more with dpiSubscrMessageTable and dpiSubscrMessage.
The text was updated successfully, but these errors were encountered: