Can't really serve static files with channels about channels HOT 8 CLOSED

The docs already say not to use DatabaseChannelLayer, but I'll reinforce it. It's really not fast with the built in Django stuff (which chunks things into 4KB chunks to serve them!)

I'm going to make it re-chunk them up to a bigger size, but yes, try the Redis backend or the in memory backend if you're just using runserver.

from channels.

Ok, I noticed it's not fast, and I am good with it (after all, debug mode ..), but it is not usable at all as it crashes the server. I am talking about an angular app so quite large assets (default main angular.js file is about 1Mo, add a few more dependencies ... ).

I'll see if can work on daphne to handle static files directly from twisted, maybe with static_dir/url option ?

from channels.

No, just use the in memory backend, it should be faster than normal runserver (channel layer asgiref.inmemory.InMemoryLayer)

from channels.

Obviously, in production, you wouldn't serve static files through Daphne anyway - I just want to make sure runserver is usable.

from channels.

All right ! much better !
Then why the "Quickstart" guide tell to use the Database layer ? . Obviously I a fast webserver for my statics, channels or not ...

from channels.

It's there because it's the only one that works with multiple processes and without installing extra things (like Redis). I hope to improve the performance of static file serving on the database backend to at least acceptable levels, though - I'll either get that to an alright level or reword it to suggest redis or memory backends.

from channels.

Wonderful, asgiref.inmemory.ChannelLayer works sufficiently well for my dev/test purposes.

I don't know if it is "large" assets, parallel fetch of them or the combination, but database backed layer fails, quasi consistently.

from channels.

The database layer needs proper transaction support to correctly do message delivery - given that you were using SQLite, it's likely that it wasn't correctly being fully serialisable and so not working!

I might just dump the database one from the docs entirely, and switch the examples to use InMemory at the start.

from channels.