[Info-vax] Marketing ideas for VSI ?
Kerry Main
kemain.nospam at gmail.com
Sat Dec 15 10:33:01 EST 2018
> -----Original Message-----
> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Bill
> Gunshannon via Info-vax
> Sent: December 14, 2018 9:45 PM
> To: info-vax at rbnsn.com
> Cc: Bill Gunshannon <bill.gunshannon at gmail.com>
> Subject: Re: [Info-vax] Marketing ideas for VSI ?
>
> On 12/14/18 9:46 AM, Jon Schneider wrote:
> > On 14/12/2018 13:41, Simon Clubley wrote:
> >> One idea I had was something along the lines of the disaster-proof
> >> video showing what VMS clusters can do. I was thinking of a demo
> >> something along these lines:
> >
> > I certainly get irritated by videos of people building clusters out of
> > Raspberry Pis running SimH with presumably no more of a concept of
> > what a cluster actually does from the client's point of view than I
have.
> >
> > My understanding is it's maybe the (Files-11) filesystem and maybe RDB
> > or something. But if that's it how is that useful in today's world
> > when the clients are web browsers ?
> >
> > So please explain what clustering actually _does_ and sell me VMS (not
> > that I am in a position to buy into it on behalf of anybody).
> >
>
> If it were me I would be pushing the concept of long distance clusters.
> Machines geographically distant so as to survive major natural and man
made
> upheavals. The biggest drawback I remember from when I was more up to
> date on this was network latency and that has really become less of an
issue
> today.
>
> bill
>
Actually network latency is primarily based on speed of light (hops also),
and this has not changed since the speed of light was originally calculated.
Other factors to consider for long distance clusters and how far apart the
can be is the R/W ration of the application This is because active-active
clusters with load balancing across both sites requires synch replication.
A heavy write app will mean you will likely need to have sites closer
together than the standard 100km rule of thumb that is usually stated in the
context of long distance clusters. This causes performance issues if a heavy
write bogs down the app while it is waiting for writes to occur at both
sites before the update is considered complete at either site.
Regards,
Kerry Main
Kerry dot main at starkgaming dot com
More information about the Info-vax
mailing list