What happens to rogue processes on streamlit share?
For instance if running locally and I terminate streamlit (ctrl c) and I still see code output to the console after streamlit has printed Stopping will this behavior eat up resources on streamlit share (inorder to kill the code I have to close the terminal window)? Or do instances get killed every time a user refreshes or navigates away from a page?
Apologies if this question is unclear and thanks for such a wonderful application!
Hi @Chris_Correll, not sure what you mean about rogue processes in this case. In terms of Streamlit sharing, the app will continue to be served until there are 7 continuous days of no traffic to the app or no commits to the app repo.
In terms of long-running processes and users navigating away, I think that the Tornado server that powers Streamlit checks for connections periodically. When it detects no active connections, then my assumption will be that the processes will stop running.
Best,
Randy
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.