[jboss-jira] [JBoss JIRA] (JGRP-2492) TimeScheduler3.add() gets more expensive as the queue size grows

[Bela Ban (Jira)]

    [ https://issues.redhat.com/browse/JGRP-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272486#comment-14272486 ] 

Bela Ban edited comment on JGRP-2492 at 7/21/20 10:43 AM:
----------------------------------------------------------

The ultimate solution would be to reactive the hashwheel based timer, plus get rid of tasks which compute their execution delay every time ({{RecurringTask}}) they're executed: the random execution time could be computed *once* (at startup), and then be used as a fixed interval (or delay) for subsequent executions.

But this is not critical, as there are not many tasks in a timer at any given time, and a task executes every coupld of hundred millis...


was (Author: belaban):
The ultimate solution would be to reactive the hashwheel based timer, plus get rid of tasks which compute their execution delay every time (\{{RecurringTask}}) they're executed: the random execution time could be computed *once* (at startup), and then be used as a fixed interval (or delay) for subsequent executions.

> TimeScheduler3.add() gets more expensive as the queue size grows
> ----------------------------------------------------------------
>
>                 Key: JGRP-2492
>                 URL: https://issues.redhat.com/browse/JGRP-2492
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 4.2.4
>            Reporter: Dan Berindei
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 5.0.0.Final
>
>
> {{TimeScheduler3.add()}} calls {{removeCancelledTasks()}}, which ends up calling {{DelayQueue.toArray()}} (because {{DelayQueue}} doesn't support directly iterating over its contents).
>  



--
This message was sent by Atlassian Jira
(v7.13.8#713008)