On 13/2/23 02:34, Hobart Spitz wrote:
IMHO, the fault lies in the character stream orientation of UNIX, C, HTML
etc. The shorted-sighted design was motivated by the limited budgets and
underpowered systems of many early UNIX users.
On record oriented systems, (z/OS and z/VM) common operations are faster,
because the needed information is not embedded in the data. For example:
- Read/skip-to the next record.
- Find/check the length of a string.
Can you please provide evidence to support that assumption?
On byte stream oriented systems, every single character, including the
otherwise uninteresting ones, must go through the CPU for such operations.
Record oriented systems can efficiently add the record length to the
current record address, or compare a target character position to the
length of the record to avoid string overflow (e.g).
What are you talking about? Writing a UNIX program that reads/writes
length-prefixed records to a file is a simple task. Do you mean to say
that all I/O performed on LUW systems involves line-delimited text files?
Anyone who understands that global warming and climate change are
existential threats and that it may be too late to avoid catastrophic
impacts would be well advised to keep their record oriented systems and
move away from UNIX, Linux, and Windows where feasible.
Arm servers outperform all competition in terms of performance per watt.
One can buy an Ampere server with 128 cores per socket, consuming an
impressively low 250W of power. A few years ago, I came across an
excellent article regarding the IBM z196, written in collaboration with
IBM. The article stated that, " "Even when aggressively cooled, the
~250W z196 dissipates over 70W of leakage, which is more than the total
power budget for many commodity server processors." Mainframes are
designed to operate at maximum capacity with redundancy integrated into
a single platform, which requires a significant amount of power.
[1] https://www.realworldtech.com/z196-mainframe/8/
Just my "buck three eighty", or two cents if you prefer.
OREXXMan
Q: What do you call the residence of the ungulate with the largest antlers?
A: A moose pad.
:-D
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands
with more than a dozen filters, while Pipelines specifications are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is the new C.
On Sat, Feb 11, 2023 at 8:37 PM Bill Johnson <
00000047540adefe-dmarc-requ...@listserv.ua.edu> wrote:
Correct. I copied the article from the NYT & then reposted the paragraph
in the article which discussed the study.
Heh - I don't think those are rankings - just (former) links from the
article in whatever publication Bill copied from.
...
The largest cloud data centers, sometimes the size of football fields,
are owned and operated by big tech companies like Google, Microsoft,
Amazon
and Facebook.
...
Over the years, data center electricity consumption has been a story of
economic incentives and technology advances combining to tackle a
problem.
Do they use:
o IBM z?
o IBM supercomputers?
o Others, such as overseas-sourced (specify)?
At one time Facebook published detailed specs for its homegrown PC servers,
in contrast to the likes of Google, Amazon, and Microsoft, for whom it's
all trade secrets. I've no idea if they've kept the specs current. Lynn
Wheeler wrote about this stuff a number of times when he was active on
IBM-MAIN, though mostly from an available-compute-power perspective rather
than a power efficiency one.
Tony H.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
