Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Amplitude client using ForkJoinPool for I/O #108

Open
kevink-sq opened this issue Aug 28, 2024 · 1 comment
Open

Amplitude client using ForkJoinPool for I/O #108

kevink-sq opened this issue Aug 28, 2024 · 1 comment

Comments

@kevink-sq
Copy link

Expected Behavior

sendEvents should use sendThreadPool instead of the default ForkJoinPool.

Current Behavior

sendEvents uses the default ForkJoinPool via CompletableFuture.supplyAsync(runnable) which scales with the number of cpu.

Possible Solution

See #107
@kevink-sq kevink-sq mentioned this issue Aug 28, 2024
Open
1 task
@kevink-sq
Copy link
Author

cc: @izaaz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kevink-sq