Config: Allow bypassing low memory suggestion #1611
Conversation
|
|
|
What threshold would you be comfortable with? We received a ton of "bug" reports by people who didn't have enough memory and no swap configured. |
I understand your concern, so I suggested not to simply reduce the threshold, but to allow user to explicitly disable it. I think that current default value of 2 GiB is reasonable, but if I want to experiment with my setup, I now have no other option other that to reduce or turn off the threshold in code and recompile the entire app. |
lastzero
added
please-test
|
I'll close this PR as I see the feature is implemented in 09f50fc |
|
Yes, I was just going to ask if you're happy with this? I've changed the variable name to |
Yes, no problem at all. Thanks! |
graciousgrey
added
released
After one of the recent releases I found out that tensorflow is disabled on my device (with 1.7 GiB of memory as reported by
free). I understand the concern, but I wanted to try to run tensorflow anyway and see how bad it is. So I added a way to bypass this check with an environment variable. I named itunsafe_to emphasize that it's not stable.It turned out that my device still can run image recognition with these resources, so I would really like to have a way to disable low memory check. I'm not very familiar with Go, so if my change is not properly implemented or can be enhanced, I'll be happy to do it.
Another note, when tensorflow is disabled because of low mem, a checkbox 'Disable tensorflow' on frontend is checked and cannot be unchecked.