Replies: 3 comments 2 replies
|
There's two different things here, but updating the cache rules for #378 to exclude these files is the best first step, I'll take a look... It's somewhat tricky to get streaming progress and caching to play nice together, but I have that on another branch right now. |
0 replies
|
I updated the cache rules & added an option to bypass the cache. This option is now used when streaming bulk files, which ensures they are rate limited but not cached. |
0 replies
|
Can we also turn down the logging - to DEBUG? This happens in some settings not all, but I think users might be bothered seeing this on every request |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
@paultiq you mentioned that caching might be causing a performance issue when downloading bulk files. Do you know why when
download_filingsis called there is a 2 minute wait before the download progress bar displays?Downloading feed file(s): 0it [00:00, ?it/s]async call made without an async bucket.
All reactions