Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LOB: use general memory buffers for storing LOB data #52

Open
bersler opened this issue Mar 19, 2023 · 3 comments
Open

LOB: use general memory buffers for storing LOB data #52

bersler opened this issue Mar 19, 2023 · 3 comments
Labels
enhancement New feature or request Low priority Low priority issues

Comments

@bersler
Copy link
Owner

bersler commented Mar 19, 2023

The current implementation does not use memory buffers to allocate LOB data. Instead heap pool is used. This leads to a situation that the total memory usage can not be limited and information presented about memory usage does not include memory allocated for LOBs.
It would be best to actually use also memory buffers for LOB.

@bersler bersler added enhancement New feature or request and removed enhancement New feature or request labels Mar 19, 2023
@bersler
Copy link
Owner Author

bersler commented Mar 19, 2023

This feature is complicated to implement.. If there is a demand from users more focus could be given here.

@bersler bersler added the enhancement New feature or request label Oct 23, 2023
@bersler bersler added the Low priority Low priority issues label Dec 30, 2023
@marlon-costa-dc
Copy link

The lack of memory buffer usage for LOB data allocation, relying instead on the heap pool, significantly affects the management of large data loads. This method leads to uncontrolled memory usage increases and lacks transparency in memory consumption metrics. Introducing memory buffers for LOB data would allow for better resource management, crucial for high-volume data environments.

Alternatively, capturing LOB data directly from the source database using a control connection could be explored, but this might be more complex and suitable as a separate feature.

Given the importance of efficient large data load management, prioritizing memory management improvements for LOBs is essential. This would greatly enhance system performance and scalability.

@bersler
Copy link
Owner Author

bersler commented Jan 28, 2024

So far this not an issue for any of OpenLogReplicator users that I am aware of. Thus the priority is low.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Low priority Low priority issues
Projects
None yet
Development

No branches or pull requests

2 participants