2 ms·
Fascinating. If the main mainframe use case is more database ops for banking or airline scheduling that doesn’t seem very compute heavy in my head so throwing h
by gigatexal 6y ago
Fascinating. If the main mainframe use case is more database ops for banking or airline scheduling that doesn’t seem very compute heavy in my head so throwing hardware at the problem makes sense especially if you can save millions to invest in development and modernization.
- shakna 6y agoI agree with you there. Most mainframe tasks today aren't that heavy on the compute - most relied on the amazing I/O stack, and that makes it easier to replace them. Heavily vectorised code with modern instruction sets can also be more performant than a lot of the older compute chips, but that requires more rewriting of code, and someone who intricately understands both the code and the math. Which makes modernising much more expensive. The VM approach is a simpler way to get you most of the way there, but replacing heavy compute stacks is usually going to require a decent bit of investment.