You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2026/01/15 18:26:00 UTC

[jira] [Resolved] (DAFFODIL-3064) Reduce Future allocation in CLI performance command

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

Steve Lawrence resolved DAFFODIL-3064.
--------------------------------------
    Resolution: Fixed

Fixed in commit e6b76fbc8bed5a794e7b2826bff81968114f2d2b

> Reduce Future allocation in CLI performance command
> ---------------------------------------------------
>
>                 Key: DAFFODIL-3064
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-3064
>             Project: Daffodil
>          Issue Type: Bug
>          Components: CLI, Performance
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 4.1.0
>
>
> The CLI performance command creates N futures, where N is the total number of files to process. So if we wanted to test the performance of 200,000 files, we create 200,000 futures.
> In profiling, this doesn't seem to make a difference, but all those Future allocations does make it more difficult to see actual allocations. Instead we should have just a single Future per thread that loops until all the input files are processed. Not only does this reduce allocations, it also matches real world usage, where there is a single serial producer and long running parallel consumers.



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