The reload speed

[v479038280]

why the reload speed is not that fast than streamlit? I almost don't need to wait in in streamlit.

Another ,the default apperance of the widget is simple but not that beautiful.

[rodja]

why the reload speed is not that fast than streamlit? I almost don't need to wait in in streamlit.

Interesting. I've not done a proper performance comparison yet. Could you share your Streamlit and NiceGUI code and how you measured it?

Another ,the default apperance of the widget is simple but not that beautiful.

We wanted the UI elements to be as frictionless as possible. Hence we stick to the Quasar defaults as good as possible. That provides the least surprises if you want to adapt. But there are a few projects which build on top of NiceGUI to offer more styled components. Like https://github.com/ofenbach/CatDesign for example.

[v479038280]

actually ,I almost don't need to wait in streamlit, I save the code ,and then switch to the brower, the result is there.But when using niceGui ,I need to wait seconds. I just run the demo from the Document. you could try almost any code in the tutorials ,the results are same.

[v479038280]

The element in QUASAR is wonderful, and the use with tailwindcss make the UI more powerfull than streamlit .It's Just the default apperance looks not that good. I should spend some time on tailwindcss and quasar.

[rodja]

I just run the demo from the Document. you could try almost any code in the tutorials ,the results are same.

For me it's quite fast. Could you try a bare FastAPI app with uvicorn and reload=True? This is what NiceGUI is using under the hood. That would help us to determine if it's a NiceGUI issue (specific to your system) or more Uvicorn related...

[v479038280]

here is a simple hello world with nicegui.

Here is uvicorn ,though I pressed the refresh, I almost can't sense the waiting time (streamlit is like this)

[rodja]

Wow, that is really slow and unexpected. This is how it looks on my side:

Is there some logging in the console? Can you share the debug log from the browser?

[falkoschindler]

The link is broken.

[v479038280]

It is OK now, but not that clear

[v479038280]

The reloading takes some time ,There is nothing wrong in the log output ,only a warn WARNING: WatchFiles detected changes in 'hello_world.py'. Reloading...

[rodja]

Can you open the debug view in the browser? JS console and network traffic would be interesting.

[v479038280]

Is this one usefull for analyse

[rodja]

Yes that may give us some leads. First I'm wondering why you get a TypeError in all.js:

We do not serve an all.js with NiceGUI. Where does it come from.

Second, you get a WebSocket connection error which is unexpected:

And the message "reloading because handshake failed" also indicates something wrong with the socket connection.

But we should first investigate the all.js. Maybe the socket error is caused by this.

[v479038280]

The all.js is from chrome-extension, look at the picture below.

Here is another demo running in firefox. No all.js

"reloading because handshake failed"

[rodja]

It's very strange to have a failing handshake. Can you try running the docker image with your code?

docker run --rm -it -p 8080:8080 -v $(pwd):/app/ zauberzeug/nicegui:1.3.8

With -v your local folder is mounted as /app. If there is a main.py you should then be able to modify it to trigger a reload.

[v479038280]

Is the speed normal?

[rodja]

Yes, thats much faster than what you showed before. There is also no failing handshake. So the problem is with your installation. Maybe remove NiceGUI (and dependencies) and reinstall?

[v479038280]

I'm now using nicegui 1.3.7, I update it to 1.3.8. There is still a handshake failed ,but the waiting time is much shorter than before.The experience was much better than before

[aersam]

Hi there
I'm also having issues with "reloading because handshake failed"

Is it possible there are some socket.io timeouts which are too low? or can we configure those?

I'm behind an azure website, so the installtion might be the problem, but I think it's unlikely . I have the issue on windows and on my linux azure website (which runs behind an IIS, tough).

[rodja]

Thanks @aersam for starting discussion about supporting "multiple workers" in #1539. Does that also explain the strange behaviour on Windows or only the Azure setup. What about you @v479038280? Does that explanation work for you, too?

[v479038280]

Actually I don't know how to remove gunicorn..

[rodja]

Can you share a minimal example of the code you are using which reproduces the problem?

[aersam]

Actually I don't know how to remove gunicorn..

Setting number of workers to one works as well 🙂

[rodja]

Wonderful. I'll close this discussion as solved. How to support multiple workers will be tackled in #1539.