Generally in most ways WebSockets will likely scale a lot better than AJAX/HTML asks for. However, it doesn’t mean WebSockets can be a replacement for many uses regarding AJAX/HTML.
Each TCP connection alone consumes almost no in phrases server sources. Often creating the connection may be expensive yet maintaining a great idle connection it really is almost totally free. The limitation is the maximum amount ports which can be open simultaneously which can be often be restricted to 64512 (65536 : 1024). Ever experimented with configuring any web server to guide 64000 simultaneous AJAX consumers? Change people clients directly into WebSockets clients plus it just could be feasible.
Though profiling our application I found a a quite strange memory usage because of the ob_start()#) functionality. We do work with ob_start()#) a reasonable amount to defer production of data, that is a common thing in most applications. What seemed to be unusual is of which 16 calls to help ob_start()#) in place chewing through pretty much 700kb of ram, given that the results being buffered not often exceeds 1-2kb, i thought this was quite unusual.