Multithread timeseries

[msweier]

Hi Guys,

Here's a first crack at adding multithreading.

1. Multi-threading to get_timeseries

• The function defaults to multi-threading and defaults to 20 threads and will chunk data by 14 days (assuming 15 minute data). It uses a helper function get_ts_extents from the catalog to check the extents of the timeseries to prevent requesting data for times outside the extents.

2. Multi-threading to store_timeseries

• The function defaults to multi-threading and defaults to 20 threads and will chunk data by 700 values (~14 days of 15 minute data). If it fails to store, it will start to backoff on how quickly it attempts to store.

Feel free to pull and make your own changes. I used a chatbot to help with a lot of it, so the code isn't very elegant but it works (although i"m sure there's improvements to be had). It seems pretty verbose for what is.

Using the local CDA, I was able to get a 6 min non-threaded call to 20 seconds. On the national instances the performance is much worse, but I think there may be some server limiting and performance issues on those.

I imaging we would want some tests for this, but I thought it would be good to get some input first.

[msweier]

Ok cleaned up the code a bit so its easier to follow and bumped up the default number of threads to 30 which work better on test and the national CDA for some reason.

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[msweier]

Replaced by #219