Tom Schmidt wrote: > One thing for you to consider, R.S., is that Poland is approximately the > size of Wisconsin. Our usage extends beyond our borders - worldwide, > actually. Because of the reach across many timezones we are more likely to > see substantial variability in usage from Linux instance to Linux > instance. If you only work within one timezone you might not find the same > opportunities.
this is similar to the vm operational data from the late 60s and early 70s. there were lots of share presentations about peak useage spikes ... typically between 10-11 in the morning and 2-3 in the afternoon. http://www.garlic.com/~lynn/subtopic.html#timeshare the internal HONE system saw similar characteristics in the early to mid 70s ... i.e. HONE was vm platform providing sales, marketing, and field support (eventually world-wide with datacenters all over the world; by the mid-70s, mainframes were getting so complex, that orders couldn't even be manually created but had to be run thru hone applications). http://www.garlic.com/~lynn/subtopic.html#hone some of the vm commercial time-sharing services had acquired international market by the mid 70s and so the peaks periods start to have a wider spread. the international clients by the mid-70s also started to create 7x24 demand ... and normal mainframe PM/service becameing real hassle. by the mid-70s some of the commercial time-sharing services had made extensive availability enhancements to vm ... lots of clustering support, including being able to migrate live workload/sessions off a processor complex that was scheduled for service/pm downtime. in the late 70s, the US hone operations consolidate their vm datacenters in northern cal. with several vm cluster operation enhancements (possibly considered the largest single system system operation in the world at the time). the consolidated us hone operation then started to see the morning and afternoon peak useage "rolling" across the US time-zones ... eastern timezone morning peak started at 7am at the cal. datacenter and then the morning peak useage rolled across the times zone until the end of the 10-11 pacific morning peak was dropping off ... just in time for the eastern timezone afternoon peak to pick up. in the very early 80s, the issue of the effect of local natural disasters on availability resulted in the US HONE complex being replicated ... first with one in Dallas and then with one in Boulder (eventually with load-balancing and fall-over between the centers). Sometime in the early 80s, I believe Jim Gray had published a paper that hardware failures were no longer the major contributing factors in system available. by that time, Jim had already left research and the system/r project (original relational/sql implementation done on a vm platform) http://www.garlic.com/~lynn/subtopic.html#systemr and had moved on to tandem. .... for some drift ... one might claim that my work on supporting hone and their clustering and availability requirements ... and my wife having served a stint in pok in charge of loosely-coupled architecture and having created peer-coupled shared data architecture http://www.garlic.com/~lynn/subtopic.html#shareddata contributed heavily to what we did later with ha/cmp product http://www.garlic.com/~lynn/subtopic.html#hacmp ... as well as having done some of the work on system/r ... helped with doing global lock manager and scale-up work for ha/cmp ... minor ref http://www.garlic.com/~lynn/95.html#13 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
