replace creation of new HTTPClient objects for each Beacon.send() (e.g. by pooling HTTPClient objects)
@thomasgrassauer is already working on this.
Since Nov 5, 2017.
Assessment
This issue has not been assessed yet.
Description
right now a new HTTPClient object is created for each Beacon.send() call. given that usually the number of different server IDs is very limited (~3) and the monitor name is hardly ever changed, I suggest e.g. pooling of the HTTPClient objects.
- Dominant language
- Java
- Stars
- 37
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Dynatrace/openkit-java
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Dynatrace/openkit-java#208 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
Dynatrace/openkit-java#207 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Dynatrace/openkit-java#206 · 3 comments · 1 reaction ·
-
Dynatrace/openkit-java#204 · 6 comments · 1 assignee ·
All issues in Dynatrace/openkit-java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·