> Le 9 févr. 2016 à 01:27, Richard Gaskin <ambassa...@fourthworld.com> a écrit : > > Pierre Sahores wrote: > > > Story made short : Appart the amazing Lua platform (preferably set as > > an Openresty one), well configured LC application’s servers still > > outperforms anything available around (Websphere, Tomcat, PHP5/7, > > Perl5, NodeJS, Go, Python, RoR,…). In-between, LC application’s > > server is 60 times faster than the stock’s Livecode CGI Server. > > Using Nginx as the load balancer of the same LC app running on > > clustered front-end servers can make a very reliable scalable > > configuration : 1500 connections for each server added to the > > cluster. In taking care to scale the ACID-SQL backend cluster as > > attendee, the platform can handle very high-end solutions at a > > fraction of the cost of more known main stream proposals. > > Can we have the story made long? :)
Only related to the test config set-up using voluntarily a very minimalistic cluster of 3 low-powered boxes. Nginx does perfectly the load-balancer job (very low top average) but OpenLiteSpeed should have being a good proposal too in the same rôle (untested), where lighttpd or apache2 seemed less productive, at least, at first glance. > > What do you mean by "LC application’s servers"? A socket server? Precisely. > Can you share some code? Not at this time. The final release will probably not rely on a PHP sockets proxy script anymore but on a direct FastCGI set-up with the advantage to provide a way to relaunch automatically the app’s sever instances in case of need; an ExternalAppClass directive will replace the PHP sockets proxy script in the new set-up. Each app node will rely on its own localhost web server instead of on the currents ones, for yet, running on the box witch hosts the Nginx proxy server. The ACID-SQL back-end cluster will, in a first time, runs only a PostgreSQL 9 instance and, if needed, (but i’m reserved on this point, as long as PostgreSQL should be able to handle 10 of thousands of connections at once without stress), a master instance dedicated to write operations and two slave nodes dedicated to read operations and master writes replications (one box peer PostgreSQL instance). To avoid unwanted side-effects, this configuration will not rely on UDP sockets « à la Oracle VLAN’s » at all to synchronize data flows in-between db nodes. Cheers, Pierre > > Exciting stuff - eager to learn more.... > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
