JS Client app & busy Omnis server
On Tue, Nov 21, 2017 at 4:43 PM, Vik Shah <Vik@keys2solutions.com.au> wrote:
> Hi Mayada,
> > We do run a very complex form (as an app) with multiple tabs, so seeing
> > this issue only at sites with high number of users might explain the need
> > to put a cap on the connection # allowed to a single server.
> To elaborate more, the app that I was working with had over 75+ remote
> forms and over a few hundred sub windows instantiated per user. 🙂
> But we also maintained our own form stack too.
> > Do you run a separate server to fork the connections to the right server
> > when it reaches max number of conn.? or how do you control that?
> We broke up the runtimes to smaller chunks, e.g. a 50user runtime was
> broken up into 10 5user runtime licences and we used Omnis LSP to then
> delegate incoming connections.
I’m not clear on what you just wrote. Did you deploy one server per 5
concurrent users and use some sort of load-balancer, this LSP, whatever
that is, in front of the cluster of servers? If so, that would mean 11
servers, assuming you don’t have any redundancy of the load-balancer. Also,
I’m not sure why the number of remote forms and sub-windows has any bearing
on this issue. Why do you think that is relevant?
Manage your list subscriptions at lists.omnis-dev.com