[
https://issues.apache.org/jira/browse/IGNITE-17274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561728#comment-17561728
]
Pavel Tupitsyn edited comment on IGNITE-17274 at 7/2/22 9:19 AM:
-----------------------------------------------------------------
Merged to master: 3e5cd22187814a1cf23d719fca37d709c0c15311
[~artnaseef] thank you for the contribution!
was (Author: ptupitsyn):
Merged to master: 3e5cd22187814a1cf23d719fca37d709c0c15311
[~artnaseef] than you for the contribution!
> Startup of large numbers of servers slowed by linear lookup in
> IgniteServiceProcessor
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-17274
> URL: https://issues.apache.org/jira/browse/IGNITE-17274
> Project: Ignite
> Issue Type: Improvement
> Components: managed services
> Affects Versions: 2.13
> Reporter: Arthur Naseef
> Assignee: Arthur Naseef
> Priority: Major
> Fix For: 2.14
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
