[jdt-dev] Potential executor service overhead

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jdt-dev] Potential executor service overhead

From: Gayan Perera <gayanper@xxxxxxxxx>
Date: Tue, 3 Mar 2020 20:06:50 +0100
Delivered-to: jdt-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jdt-dev>
List-help: <mailto:jdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jdt-dev>, <mailto:jdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jdt-dev>, <mailto:jdt-dev-request@eclipse.org?subject=unsubscribe>

Hi All,

According to the how executor service is handled in org.eclipse.jdt.internal.ui.text.java.ChainCompletionProposalComputer.executeCallChainSearch() it can be a overhead until the GC collects it in the best case. Because the shutdownNow is only called if a timeout or execution error is raised.

Should i raise a bug for this ? Or am trying to over optimize it ?

Br,

Gayan.

Follow-Ups:
- Re: [jdt-dev] Potential executor service overhead
  - From: Roland Grunberg
- Re: [jdt-dev] Potential executor service overhead
  - From: Andrey Loskutov

Prev by Date: [jdt-dev] Figuring out a Type is forbidden or not
Next by Date: Re: [jdt-dev] Potential executor service overhead
Previous by thread: [jdt-dev] Figuring out a Type is forbidden or not
Next by thread: Re: [jdt-dev] Potential executor service overhead
Index(es):
- Date
- Thread

Breadcrumbs