[Info-vax] How would you load balance excess webserver traffic between multiple OpenVMS servers?
Arne Vajhøj
arne at vajhoej.dk
Mon Jan 11 11:23:30 EST 2021
On 1/11/2021 9:45 AM, Marc Van Dyck wrote:
> Arne Vajhøj expressed precisely :
>> On the web servers you need the application code & data to stay resident
>> in memory and reuse threads/processes to process requests as
>> starting processes and loading images are expensive. And
>> the database connections need to be managed by a connection pool
>> as open connection is expensive (note that a connection pool
>> also require application code& data resident in memory).
>>
> Wasn't ACMS made to solve just that problem ? Has one already tried to
> implement a web server with ACMS - assuming anyone still knows the
> product, that is ?
I know little about ACMS, but it is my clear impression that it
is way more than a database connection pool.
A database connection pool is really a simple concept.
Without pool: request processing opens a physical connection
to the database, do what it need to do and closes connection.
With pool: at startup N connections are made, request processing
borrows a connection from the pool use it and return it.
There can be some bells and whistles with pool size
increasing and decreasing over time depending on demand,
the pool making keep alive queries, failover handling etc. -
but the basics are very simple.
Arne
More information about the Info-vax
mailing list