DiggidyDave commented on issue #9190: [SIP-39] Global Async Query Support
URL: 
https://github.com/apache/incubator-superset/issues/9190#issuecomment-591235866
 
 
   I'm sure you've seen all of this @robdiciuccio but leaving it here for the 
general audience, it touches on a lot of the tradeoffs discussed here: 
https://moduscreate.com/blog/fast-polling-vs-websockets-2/
   
   I had forgotten that the polling transport used long polling. :-/ I think 
there are some options you can configure on the transport, but I'm less 
confident now that short-polling with socket.io is an option. When I used it 
previously, we were using websockets (not long polling) on `gunicorn` and 
`gevent` but we were not using any datasources so I can't speak to that 
specifically. But we did have to actually write code on the server side to 
manage some concurrency issues (like explicitly sleeping to yield the processor 
in certain places to keep things moving) so it might make sense that some db 
drivers are not out-of-the-box compatible if running in the same process as the 
socket server.
   
   I know I said I had said my 2 cents, but a couple more questions came to 
mind (sorry!):
   - are "many tabs" really a problem? do we need to be polling/streaming 
events constantly for inactive tabs? If only the 1-3 (for power users) active 
tabs a user will have are the ones we care about, could we only actively 
short-poll only on those active tabs (using page visibility apis)? upon 
switching tabs, a quick single, first poll request will see if results have 
come in for the new tab and cause them to be immediately fetched
   - if the above is true: if polling is active only for active tabs, and 
batched for dashboards, what are the remaining problems that require websockets?
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to