Building a fully functional SAP system just takes that long in raw install time when your process also includes a sufficiently large system copy, and your hardware isn’t bleeding-edge.
I worked at a place once that had a system that was all bash that would take hours to run. I rewrote it in Ruby and got the run down to about 10 minutes.
This was 2000; I don’t recall anymore how much of that was the runtime and got much was just refactoring and hindsight - god knows how old that jumble of bash scripts were. A lot must have been the interpreter; even just looping is far slower in bash than probably anything else.
Not a comment on your script; just remembering that win.
I wrote and maintain a zero-to-working SAP HANA/S4 installer in pure bash.
It takes a redhat compatible from base install to a working, production-ready SAP system in about 5 hours.
It’s like ~9,000 lines of bash
Why does it take 5 hours?
Building a fully functional SAP system just takes that long in raw install time when your process also includes a sufficiently large system copy, and your hardware isn’t bleeding-edge.
It’s a massive application stack
Does that include network latency? Is it faster with install media?
I copy the install media locally. Although there is probably a noticable performance hot to running my main VM disk over the network.
I worked at a place once that had a system that was all bash that would take hours to run. I rewrote it in Ruby and got the run down to about 10 minutes.
This was 2000; I don’t recall anymore how much of that was the runtime and got much was just refactoring and hindsight - god knows how old that jumble of bash scripts were. A lot must have been the interpreter; even just looping is far slower in bash than probably anything else.
Not a comment on your script; just remembering that win.
99% of the waiting time in my case is either waiting for file copies or waiting on SAP programs to run.
I wish I had low hanging fruit like that to go after.