Workiva
Change _insert_tasks to use add_async
In _insert_tasks(), we now add each task individually using
Queue.add_async(), instead of all at once with Queue.add(). This allows
us to insert each task only once and not have to worry about splitting
and retrying until we find the bad tasks. Unfortunately this method
prevents us from determining exactly how many tasks were successfully
inserted. This will help however when a large number of duplicated tasks
are trying to be added and it keeps splitting instead of just quitting.
This looks pretty good. I assume this helps speedup some of our worst cases.
Do we want to make this optional? I'd hope we wouldn't need to make it optional if this works well.
Does the developer sometimes want to ensure the tasks have been inserted? Maybe storing the futures on the class would allow a developer to make get_result calls? - I'm not sure if keeping those handles would use more memory.
Also, any memory bloat by using many single add_async() instead of one group add()?
As @beaulyddon-wf noted, you need to run some more tests. Specifically I would like to see "normal" case tests, meaning there are no splits, just a single successful batch insert.
I would also like to see how the async-per-task compares with one, ten, one hundred, one thousand tasks. If you add the get_result call in, how does this compare?
