-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Tiled server timeout #96
Comments
FYI @Wiebke |
Hit again today multiple times while running app locally after panning around to view different slices of the lobster claw dataset.
|
I can confirm this has been happening as well on my end during local development. |
And every once in a while I get this error:
|
It sounds to me that read timeout is hitting it's default 5 seconds for these requests, and that we're not seeing it because we're closer to the service, maybe? Can you try changing the default timeout? The tiled client uses the import httpx
client = from_uri("http://localhost:8000/", api_key=<key>, timeout=httpx.Timeout(60.0))
|
Other (and third type of error) Ive been getting:
|
Sorry about that. It looks like an issue in Tiled. I think that have gotten around it be reducing the number of Tiled pods in our setup to just 1. (If you're curious, I reported the issue here ). Can you try again? |
@dylanmcreynolds @Wiebke I'm also still getting that Are there any other strategies that we can look into to improve the consistency of performance on the Tiled server? Client-side caching might help a bit here. |
@hannahker, for the 500 errors, there is a clear path, but it will take some time, and I am unfortunately on the road next week. For the timeouts and data rates, there are two strategies, one that we can tackle on the server, and one that you can probably tackle in dash.
object_cache:
available_bytes: 2_000_000_000
log_level: DEBUG
|
We've addressed this for now by enhancing the data available when running a local Tiled server. This is a suitable workaround for our local development, but we're still hitting these issues frequently on the apps deployed to our servers, making it difficult to properly test our work in a deployed environment. |
See additional comments on client-side caching in #133 |
Have noticed some timeout errors in the Tiled https requests since updating the Tiled server version:
httpx.ReadTimeout: The read operation timed out
. This is present both locally and on the deployed app (deployed on Plotly's servers). Some more testing is needed to see if this can be reproduced reliably.The text was updated successfully, but these errors were encountered: