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
Currently we the allocation/de-allocation logic does unneccessary memory copy causing CPU load and on top we need double the heap size than it actually requires in usual cases.
Let's say we configure the dlt buffer size as 20 MB, we need approx 40 MB during the allocation of the final step size.
Same logic is used in dltlib, this all applications are also affected due to this inefficient logic.
We need to improve it.
The text was updated successfully, but these errors were encountered:
anoojgopi
changed the title
Imrovement to be done on dlt internal buffer allocation logic
Improvement to be done on dlt internal buffer allocation logic
Jan 24, 2018
@anoojgopi Sorry that we haven't replied to your request for long time. The allocation/deallocation should only happen in rare cases; the daemon is not alive yet, some issues in socket/fifo buffers, too much logging happening, etc. If it is happening often for a specific dlt-user, the application should be configured with the env variables in a way that it does not happen anymore:
Currently we the allocation/de-allocation logic does unneccessary memory copy causing CPU load and on top we need double the heap size than it actually requires in usual cases.
Let's say we configure the dlt buffer size as 20 MB, we need approx 40 MB during the allocation of the final step size.
Same logic is used in dltlib, this all applications are also affected due to this inefficient logic.
We need to improve it.
The text was updated successfully, but these errors were encountered: