JS Client app & busy Omnis server

That is a moot question, especially with Studio 4.x. It was leaky as hell.

Regardless of Server(32 core cpus)/OS(Windows 2012)/Resource management tools it was a unique set of circumstance that led Omnis Studio 4.x to become unstable and consume lots of memory, especially when reporting came into play. But that is history now… (for me at least as I’ve moved on from that project a few years ago)

I’ve just shared my experience in the hopes that some parts of it may help Mayada or anyone out there. 🙂

Vik Shah

> On 22 Nov 2017, at 10:13, Clifford Ilkay <cilkay@gmail.com> wrote:
>
> What kind of resources are you allocating to these servers and which OS are
> you running on?
>
> Regards,
>
> Clifford Ilkay
>
> +1 647-778-8696
>
> On Tue, Nov 21, 2017 at 7:00 PM, Vik Shah <Vik@keys2solutions.com.au> wrote:
>
>> Hi Clifford,
>>
>> I can elaborate…
>>
>> Take a 50 user licence and get Omnis to give you 10 5-user licences. Then
>> run various omnis web server runtimes (either on the same physical box or
>> different boxes) and use the Omnis Load Sharing Processor to mange where
>> the connection goes.
>>
>>> 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?
>>
>> It does, if you have an interface heavy application then the amount of
>> memory used per user by Omnis is high. The complex your design is the
>> higher the memory usage is, this counts for both visual and non-visual
>> complexity.
>>
>> I must say that this was for Studio 4.x environment but I am confident
>> that it still applies (to some degree) for Studio 6.x too. Not sure about
>> 8.x though as there have been huge improvements with the Omnis codebase.
>>
>> Vik Shah
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com