However, I only intended this model to be a ‘placeholder’ whilst I experimented with others. The model I actually want to use is a fine-tuned bert-large! But when I tweak my code so that the Streamlit app points at the larger model instead, I get an error during deployment.
The service has encountered an error while checking the health of the Streamlit app: Get “http://localhost:8501/healthz”: dial tcp 127.0.0.1:8501: connect: connection refused
I’m assuming that this must be due to the difference in model size, as this is the only thing that has changed. However, could someone confirm this, and maybe advise on what can be done to get Streamlit to load the larger model?
It looks like your app’s memory usage is around 1.5GB, so it is likely that the size of the model is causing the issue. I’d recommend using caching as much as possible to avoid loading the model multiple times. Do you know the approximate size of the model?
Hi @Caroline, thanks for your message. So, this makes sense as the size of the model alone is about 1.35gb – which I guess already exceeds the standard allowance for Streamlit accounts?
I’m already caching the model in my code, but I guess with a model this size no amount of caching is going to help?
Is there any way to increase the memory allowance for my account? (I’m a university student working on a monkeypox misinformation classifier, if that helps in terms of it being an NFP / public interest project.)
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
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.
Performance cookies
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.
Functional cookies
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.
Targeting cookies
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.