amit-handda

thanks folks, this is nice. I am looking to adopt db-scheduler and pair it up with kotlin coroutines to execute short tasks which are going to mainly interact with 2-3...

@kagkarlsson we created a PR to address this issue, would be awesome if you could review it sometime. TYSM https://github.com/kagkarlsson/db-scheduler/pull/304

As expected, we have observed signficant throughput gains for async tasks, as follows:   | Current (execution/s) | Future-based (execution/s) -- | -- | -- 1 scheduler instance |   |   300...

Hello @kagkarlsson, hope you had nice vacation. Wondering if you are back and had the time to look at the PR ? Let me know if you have any query....

Hello @kagkarlsson , thanks for the feedback. ques 1/ how do you intend the `ExecutionHandler` interface to be ? The PR is allowing the `ExecutionHandler` implementation to return a Future...

> > I need to understand why a future-based execution will be that much faster. Feels like we are skipping av step.. Hi, It is due to our task defn....

> Well, that is the problem, I do not know currently. What options do we have 🤔 IMO, returning a `completablefuture` is the only option to enable task to execute...

Hi @kagkarlsson, we used lock_and_fetch poll strategy with 0.5 (lower_limit) and 4.0 (upper_limit). please let me know if you need more info. Many thanks for your careful review feedback. Have...

@kagkarlsson * digging deeper into ```unexpectedly high executions/s```, ll get back to you * about async-mod via config setting ... not sure about it, as discussed earlier. the PR makes...

Thanks @kagkarlsson I agree with this, we can let it breathe through custom branch please.