I appreciate the background. Now, from the flip side, I’ve been programming professionally since '78 - I learned how to write code using an IBM-029 keypunch system. I can’t count the number of different hardware and software platforms that I’ve had my fingers in over the years.
My career path has taken me through three different supervisory / managerial positions along with stints as an Information Security Officer and as an Enterprise Systems Architect. (Fancy titles for jobs consisting mostly of pushing paper.)
There are some constants that I’ve observed universally over that time, and one of them is for some programmers to develop a preoccupation with “micro-optimizations”. If you’ve got a sub-optimal algorithm, that’s going to have significantly more effect on overall throughput than worrying about minor details. Saving 250 milliseconds on a request taking 5000 is just not going to create a noticeable improvement.
Bottom line is that any effort to optimize performance at this stage is completely misplaced. You don’t know where your bottlenecks are going to be until you have a system up and running and can actually measure the performance of your system.
You’ve got time. There is nothing you’re going to be able to tell me that will convince me otherwise.
Get your system up and running. Build your test stack to see how it will perform under load. Then measure the performance of the different components within your system, identify the bottlenecks and spend your time addressing them.
That’s 43 years of directly applicable experience trying to explain why your efforts and attention to that topic is, at this time, misplaced.