I have a small dash app currently hosted on Google Cloud Run, with two pages [internalFeed, adminFeed] with a handful of graphs/tables each. I am capturing the dynamic variable in the pathname (/internalFeed/). The ecosystem variable is passed through a callback to retrieve data from:
1 cloud mysql table where rows range from the low 100s to edging towards 200k rows and ~10 columns
3 tables on SupaBase, each ranging from the low hundreds to rarely over 1200 rows. and each ~12 columns.
Our team is restructuring some data architecture so they will be consolidating in the next quarter.
The internalFeed page allows a dropdown to select through 1 of the many ecosystems to display data on in a stacked barchart and two tables, the adminFeed page is similar, but uses a few more tables. The data is aggregated and slimmed down to a small reporting style, rarely more than a few hundred datapoints each.
Running locally there is sometimes ~10 seconds of lag when switching between different ecosystems, but hosted on cloud run the app often fails to load, and shuts down. There are usually POST 500 errors on the logs when attempting to update a callback.
I’m not entirely where to start or what information I can provide that will be helpful. Thanks in advance!
Locally, it’s a sporadic dance with lag, but when launched into the Cloud Run cosmos, it’s a celestial challenge. The app occasionally falters, invoking POST 500 errors during callbacks, particularly when navigating diverse ecosystems. It’s a cosmic riddle, and I’m reaching out to the Plotly galaxy for unconventional wisdom.