-
Notifications
You must be signed in to change notification settings - Fork 38
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
Updated Willow (though WAS) and also WIS on server. #121
Comments
Stopped WIS and WAS. Nothing - no response from the S3 devices. Not even a reponse back from WIS. |
The PROBLEm is the BEAM size....! a while back someone on the github response wold me to use BEAMsize=5. Well, starting up the server, I noticed it uses BEAM-SIZE=1. So I modified my config, flash the S3-lite with beam-size=1 and it magically worked. WHAT is the difference - why did the beam size owrked before with 5 and not it requires 1? |
We've never made an API change between Willow and WIS so I'm not sure why anything with the releases should matter. Beam size tweaks a parameter inside the model more-or-less regarding accuracy. People throw a lot of things around on Github, the internet, etc but the medium model with beam_size=1 is the current WIS default. We've been doing extensive testing and the next release of WIS will actually default to small beam_size=2. That said we also routinely test all of the possible model and beam_size configurations. I've never seen and we've never had reports of there being issues with any of the models or beam sizes, the only thing I can think of is larger models and larger beam sizes use more GPU memory. What model of Nvidia GPU do you have? We do a lot on WIS startup to define parameters for even really low VRAM and older GPUs, I myself extensively test with a GTX 1060 6GB which is towards the lowest GPU we could support. Also, you probably want to be a little more careful randomly upgrading Nvidia drivers. We have extensive compatibility with Nvidia drivers as well (we test with 525-535 on Ubuntu) but like all driver upgrades there can definitely be lower-level difficult to debug issues from swapping random drivers around. |
I am running WIS on a GTX 1080Ti. |
The GTX 1080Ti has 12GB VRAM which is enough to run several instances of WIS concurrently, you definitely shouldn't be having any issues running any models at any beam size. Your issue with beam size five does point to some kind of strange card/driver quirk we have never seen before. I mentioned doing Nvidia driver upgrades carefully in the general sense as there is definitely potential to encounter some rough edges given how fundamental they are. It's generally safe but every once in a while things go wrong. |
I think the Nvidia drivers could have been the issue as I updated the ESP-
Willows and WIS, before I did a system upgrade.
But even after I did the driver update and reboot, WIS still defaults to
Beam-size=1. And when size=5 is specified in willow, WIS rejects the
response.
Is there a way to chance the default size in WIS, it seems that it must be
an option for this, but I do not know where to look for it? In utils.sh?
Thanks
Bert
…On Wed, Sep 27, 2023, 07:01 Kristian Kielhofner ***@***.***> wrote:
The GTX 1080Ti has 12GB VRAM which is enough to run several instances of
WIS concurrently, you definitely shouldn't be having any issues running any
models at any beam size. Your issue with beam size five does point to some
kind of strange card/driver quirk we have never seen before.
I mentioned doing Nvidia driver upgrades carefully in the general sense as
there is definitely potential to encounter some rough edges given how
fundamental they are. It's generally safe but every once in a while things
go wrong.
—
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEN5KAAMXXUV27JY2CQURJTX4QPTTANCNFSM6AAAAAA5IL5KHM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@bert269 - It is still very strange you're having problems with On another note, you almost certainly don't need and probably don't want |
I had to re-install everything this rmorning. I will test this out as soon as I get the other issue resolved and provide feedback. |
Then I updated to the latest (willow-RC2) software on each of the ESP32-S3 (and one S3-lite) device and none is responding. They respond to the wakework, but just sits there. This is a screenshot from what's happening on WIS:
I'll flash the previous RC-1 to the first S3 and see what happens. All the willow were working fine still this morning, util I updated everything.
The text was updated successfully, but these errors were encountered: