Taeho Kim <dittos@gmail.com>: Author Summary

Builds triggered by Taeho Kim <dittos@gmail.com>

Builds triggered by an author are those builds which contains changes committed by the author.
3
1 (33%)
2 (67%)

Breakages and fixes

Broken means the build has failed but the previous build was successful.
Fixed means that the build was successful but the previous build has failed.
1 (33% of all builds triggered)
0 (0% of all builds triggered)
-1
Build Completed Code commits Tests
REACTOR › RNEXT › #2646 1 week ago
fix #1938 Remove overeager toString calls in FluxIndexFuseable
The Objects.requireNonNull on the result of the index mapper would
eagerly call toString on each element to construct the message, which is
wasteful.

A solution similar to what was done on the non-fuseable version in #1456
is applied.
5614 passed
REACTOR › RNEXT › #2543 4 months ago
fix #1722 Make sure ElasticScheduler.CachedService gets disposed
When schedule is called, a CachedService is acquired first.
It is disposed after the task is run. However, if the task is not run
(because of immediate disposal), CachedService is not disposed.
This commit fixes that.

Reviewed in: #1724
5439 passed
REACTOR › RNEXT › #2506 5 months ago
fix #1700 Improve cache eviction in ElasticScheduler
Currently `ElasticScheduler` uses a queue to manage the cache of
executors. When a task is finished, the free executor gets enqueued to
the queue with ttl. When a new task is scheduled, a cached executor is
dequeued from the queue (which has the oldest ttl).

Therefore an executor with the highest chance of getting evicted is
removed from the queue for reuse, which leads to the problem that
executors are unable to get evicted if tasks are scheduled at some rate
faster than `ttlSeconds`.

This commit replaces queue with deque and reuse executors in LIFO order.
Using deque may have small memory overhead of backward pointer per deque
entry, but it is much smaller than keeping unnecessary thread around.
I assume that performance hit is also small.
1 of 4992 failed
Build Completed Code commits Tests
REACTOR › RNEXT › #2506 5 months ago
fix #1700 Improve cache eviction in ElasticScheduler
Currently `ElasticScheduler` uses a queue to manage the cache of
executors. When a task is finished, the free executor gets enqueued to
the queue with ttl. When a new task is scheduled, a cached executor is
dequeued from the queue (which has the oldest ttl).

Therefore an executor with the highest chance of getting evicted is
removed from the queue for reuse, which leads to the problem that
executors are unable to get evicted if tasks are scheduled at some rate
faster than `ttlSeconds`.

This commit replaces queue with deque and reuse executors in LIFO order.
Using deque may have small memory overhead of backward pointer per deque
entry, but it is much smaller than keeping unnecessary thread around.
I assume that performance hit is also small.
1 of 4992 failed
Build Completed Code commits Tests