You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Marton Szasz (Jira)" <ji...@apache.org> on 2025/04/25 15:30:00 UTC

[jira] [Resolved] (MINIFICPP-2541) Simplify VolatileContentRepository

     [ https://issues.apache.org/jira/browse/MINIFICPP-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marton Szasz resolved MINIFICPP-2541.
-------------------------------------
    Resolution: Done

> Simplify VolatileContentRepository
> ----------------------------------
>
>                 Key: MINIFICPP-2541
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-2541
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Adam Debreceni
>            Assignee: Adam Debreceni
>            Priority: Major
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Currently VolatileContentRepository is a ring-buffer with a fixed maximum size, overwriting data when "full". This is undesirable, and to circumvent this, users utilize connection-level constraints (max data size, max count) to prevent this. We should utilize these connection-level limitations only and let the repository otherwise grow unconstrained. Performance measurement indicate that this can give a 2X performance improvement as a bonus.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)