Re: architectural goals, Byte Addressability And Beyond

Liste des GroupesRevenir à c arch 
Sujet : Re: architectural goals, Byte Addressability And Beyond
De : SFuld (at) *nospam* alumni.cmu.edu.invalid (Stephen Fuld)
Groupes : comp.arch
Date : 07. Jun 2024, 04:13:54
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v3ttti$1tiem$1@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : XanaNews/1.21-f3fb89f (x86; Portable ISpell)
Lawrence D'Oliveiro wrote:

On Thu, 6 Jun 2024 11:55:22 -0000 (UTC), John Levine wrote:
 
If you're doing something that is mostly read-only and easy to
parallelize, then it makes sense to use a farm of cheap PCs. But if
you are a bank or an airline, you need to be able to lock your
database so that you debit a bank account or sell a plane seat
exactly once.  There is a rule of thumb that the cost of locking
something grows roughly as the square of the number of things
contending for the lock.
 
Remember that the number of users actually buying a product at any
given time is only a small proportion (say 1%) of the number of users
currently accessing the site.

I don't know where you got that number, but even if it is true for a
retail storefront type site, I am pretty sure it isn't true for a bank
(what John was talking about, and a substantial part of mainframes's
user base).  Few people "browse" bank's the products.  :-)  Even for an
airline (the other example John gave.) I suspect that far more than 1%
of the accesses are updates.



--
 - Stephen Fuld
(e-mail address disguised to prevent spam)

Date Sujet#  Auteur
31 May 24 * Re: architectural goals, Byte Addressability And Beyond42John Savard
31 May 24 `* Re: architectural goals, Byte Addressability And Beyond41John Levine
1 Jun 24  +* Re: architectural goals, Byte Addressability And Beyond31John Savard
1 Jun 24  i+* Re: architectural goals, Byte Addressability And Beyond20Thomas Koenig
2 Jun 24  ii+* Re: architectural goals, Byte Addressability And Beyond6John Savard
2 Jun 24  iii`* Re: architectural goals, Byte Addressability And Beyond5Thomas Koenig
2 Jun 24  iii +* Re: architectural goals, Byte Addressability And Beyond3John Levine
3 Jun 24  iii i`* Re: architectural goals, Byte Addressability And Beyond2OrangeFish
3 Jun 24  iii i `- Re: architectural goals, Byte Addressability And Beyond1John Levine
4 Jun 24  iii `- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro
4 Jun 24  ii`* Re: architectural goals, Byte Addressability And Beyond13Lawrence D'Oliveiro
5 Jun 24  ii `* Re: architectural goals, Byte Addressability And Beyond12Lawrence D'Oliveiro
5 Jun 24  ii  +- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro
6 Jun 24  ii  `* Re: architectural goals, Byte Addressability And Beyond10George Neuner
6 Jun 24  ii   +* Re: architectural goals, Byte Addressability And Beyond6John Levine
7 Jun 24  ii   i+* Re: architectural goals, Byte Addressability And Beyond4Lawrence D'Oliveiro
7 Jun 24  ii   ii`* Re: architectural goals, Byte Addressability And Beyond3Stephen Fuld
7 Jun 24  ii   ii `* Re: architectural goals, Byte Addressability And Beyond2Lawrence D'Oliveiro
7 Jun 24  ii   ii  `- Re: architectural goals, Byte Addressability And Beyond1Stephen Fuld
7 Jun 24  ii   i`- Re: architectural goals, Byte Addressability And Beyond1Terje Mathisen
6 Jun 24  ii   +- Re: architectural goals, Byte Addressability And Beyond1Lynn Wheeler
6 Jun 24  ii   +- Re: architectural goals, Byte Addressability And Beyond1OrangeFish
7 Jun 24  ii   `- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro
2 Jun 24  i`* Re: architectural goals, Byte Addressability And Beyond10John Dallman
2 Jun 24  i `* Re: architectural goals, Byte Addressability And Beyond9Thomas Koenig
2 Jun 24  i  `* Re: architectural goals, Byte Addressability And Beyond8John Dallman
3 Jun 24  i   `* Re: architectural goals, Byte Addressability And Beyond7Anton Ertl
3 Jun 24  i    `* Re: architectural goals, Byte Addressability And Beyond6John Dallman
3 Jun 24  i     `* Re: architectural goals, Byte Addressability And Beyond5Michael S
5 Jun 24  i      `* Re: architectural goals, Byte Addressability And Beyond4John Dallman
5 Jun 24  i       +- Re: architectural goals, Byte Addressability And Beyond1Michael S
5 Jun 24  i       `* Re: architectural goals, Byte Addressability And Beyond2Anton Ertl
5 Jun 24  i        `- Re: architectural goals, Byte Addressability And Beyond1MitchAlsup1
2 Jun 24  +- Re: architectural goals, Byte Addressability And Beyond1Michael S
2 Jun 24  +- Re: architectural goals, Byte Addressability And Beyond1John Dallman
4 Jun 24  `* Re: architectural goals, Byte Addressability And Beyond7Lawrence D'Oliveiro
4 Jun 24   +- Re: architectural goals, Byte Addressability And Beyond1John Levine
5 Jun 24   `* Re: architectural goals, Byte Addressability And Beyond5John Dallman
5 Jun 24    +- Re: architectural goals, Byte Addressability And Beyond1Michael S
6 Jun 24    `* Re: architectural goals, Byte Addressability And Beyond3Lawrence D'Oliveiro
6 Jun 24     `* Re: architectural goals, Byte Addressability And Beyond2MitchAlsup1
6 Jun 24      `- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal