On Sat, Mar 24, 2018 at 11:30 AM Matteo Merli
wrote:
> One other thing that is not clear to me is why we need delayed execution
> AND key ordering.
>
> Shouldn't be fine to retry later in a random thread? If the requirement is
> to do something from a specific thread, we can also jump into that t
One other thing that is not clear to me is why we need delayed execution
AND key ordering.
Shouldn't be fine to retry later in a random thread? If the requirement is
to do something from a specific thread, we can also jump into that thread
when the delay task is finally executed.
On Sat, Mar 24,
On Sat, Mar 24, 2018 at 8:38 AM, Matteo Merli wrote:
> While profiling the allocations of a BookKeeper client (from current
> master) writing entries, I've noticed that there are multiple allocations
> per entry related to the OrderedScheduler.
>
> I think OrderedScheduler was introduced in 4.6 a
Il sab 24 mar 2018, 16:38 Matteo Merli ha scritto:
> While profiling the allocations of a BookKeeper client (from current
> master) writing entries, I've noticed that there are multiple allocations
> per entry related to the OrderedScheduler.
>
> I think OrderedScheduler was introduced in 4.6 and
While profiling the allocations of a BookKeeper client (from current
master) writing entries, I've noticed that there are multiple allocations
per entry related to the OrderedScheduler.
I think OrderedScheduler was introduced in 4.6 and now OrderedSafeExecutor
is just an extension of OrderedSchedu
