[
https://issues.apache.org/jira/browse/IGNITE-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef updated IGNITE-17524:
-----------------------------------
Fix Version/s: (was: 2.14)
Description:
Cloned from IGNITE-17274. That ticket addresses startup timing, and this one
addresses shutdown timing.
Shutting down large numbers of services is slowed down by a linear lookup that
can be addressed by adding a map to perform the lookups.
was:
Using a small POC, spinning up many servers is slow. In addition, the startup
time appears to be exponential.
Using timing measurements, found a linear lookup inside the
IgniteServiceProcessor that is taking most of the time.
Replacing that linear lookup with a Map lookup, and maintaining the map,
significantly speeds up the process, and startup time is now linear with the
number of services started.
Note this was tested with 20K and 50K services on a 1-node ignite cluster.
Timings against the stock 2.13.0 code come in at 30s for 20K and 250s for 50K
services. Modifying the linear lookup to use a Map, the timing come in at 8s
for 20K and 14s for 50K services.
> Shutdown of large numbers of servers slowed by linear lookup in
> IgniteServiceProcessor
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-17524
> URL: https://issues.apache.org/jira/browse/IGNITE-17524
> Project: Ignite
> Issue Type: Improvement
> Components: managed services
> Affects Versions: 2.13
> Reporter: Arthur Naseef
> Assignee: Arthur Naseef
> Priority: Major
>
> Cloned from IGNITE-17274. That ticket addresses startup timing, and this one
> addresses shutdown timing.
> Shutting down large numbers of services is slowed down by a linear lookup
> that can be addressed by adding a map to perform the lookups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
