3 ms·

yes for general public use page 15 in this white paper from 2012 is the closest I can go in terms of naming. there were more , in continental Europe. https:/

by froh 4y ago

yes for general public use page 15 in this white paper from 2012 is the closest I can go in terms of naming. there were more , in continental Europe. https://www.slideshare.net/hcl/effective-web-hostingonzlinuxwhiteboardv1 https://www.slideshare.net/hcl/effective-web-hostingonzlinux...

Spooky23 4y ago
IBM was paying them to do it. The problem is you’re running in a separate set of processors… it’s almost like a blade chassis at this point. The cost structure didn’t work as if you’re doing anything significant you’re going to end up licensing more CPU time (yes, you need to buy access to the stuff you bought), and it cheaper to buy x86 and run Linux OR just rent VMs from Amazon. I had to do a POC of this for an IBM app in 2008-9, as it was seen as a way to save on IBM software licensing. I killed the notion after spending 6 months getting stuff to work (ie the IBM boys and inwere the first idiots to try) when i borrowed from surplus PCs awaiting shredding and replicated the entire environment on 6 circa 2005 pentium whatever desktops (which I did during the week between Christmas and New Years). My little lab outperformed the mainframe by a factor of 5 for the task. If these solutions were sold commercially, there must have been some German compliance requirement that led people to do it. Nobody would ever do this without getting directly compensated for “choosing” to do so.
- froh 4y ago
  what works financially is providing a fleet of simple similar independent machines. think "your personal wordpress instance w/ own email and ftp server", centrally maintained, identical baseline but individual content. to this day Linux KVM does not enable multi tenancy. with z/VM you can provide that, and you still have the shared /usr in physically shared ram in z/vm. the physical CPUs are also virtualized and shared, each "full own wordpress server" only needs slivers of that cpu pool. it was done and it qorkwd. and it was profitable for both the hosters and IBM.
  - Spooky23 4y ago
    Yes - that was very interesting one of the drivers for what I was working on was that the z/VM segmentation would allow for partitioning of workloads to avoid over-licensing and address some security needs. The tough part was if you didn’t have that perfect scaling opportunity, things fell down fast, and the marginal cost for more resources was way too much. IBM tried to oversell it.

by froh 4y ago

Spooky23 4y ago

IBM was paying them to do it. The problem is you’re running in a separate set of processors… it’s almost like a blade chassis at this point. The cost structure didn’t work as if you’re doing anything significant you’re going to end up licensing more CPU time (yes, you need to buy access to the stuff you bought), and it cheaper to buy x86 and run Linux OR just rent VMs from Amazon. I had to do a POC of this for an IBM app in 2008-9, as it was seen as a way to save on IBM software licensing. I killed the notion after spending 6 months getting stuff to work (ie the IBM boys and inwere the first idiots to try) when i borrowed from surplus PCs awaiting shredding and replicated the entire environment on 6 circa 2005 pentium whatever desktops (which I did during the week between Christmas and New Years). My little lab outperformed the mainframe by a factor of 5 for the task. If these solutions were sold commercially, there must have been some German compliance requirement that led people to do it. Nobody would ever do this without getting directly compensated for “choosing” to do so.

froh 4y ago
what works financially is providing a fleet of simple similar independent machines. think "your personal wordpress instance w/ own email and ftp server", centrally maintained, identical baseline but individual content. to this day Linux KVM does not enable multi tenancy. with z/VM you can provide that, and you still have the shared /usr in physically shared ram in z/vm. the physical CPUs are also virtualized and shared, each "full own wordpress server" only needs slivers of that cpu pool. it was done and it qorkwd. and it was profitable for both the hosters and IBM.
- Spooky23 4y ago
  Yes - that was very interesting one of the drivers for what I was working on was that the z/VM segmentation would allow for partitioning of workloads to avoid over-licensing and address some security needs. The tough part was if you didn’t have that perfect scaling opportunity, things fell down fast, and the marginal cost for more resources was way too much. IBM tried to oversell it.