1. It really isn't the kind of problem we are trying to solve.
2. Last time we did this we were over 100x faster and so we said. Ok its slow as &#@%.
We are more interested in trying to compare to tools that can provide workflows which are:
A. I have a ton of data in S3, HDFS, cloud storage solutions, centralized NFS
B. I want to use the GPU to perform learning, graph analytics, classification, etc.
I want to get from A to B as fast as possible utilizing the same resources for A that I will need to complete steb B.
As for size we will be releasing much larger workloads for GTC and are working hard on finishing up our work to make the workloads public and reproducible as well as releasing a new version of our engine where you can run much much larger workloads through distribution.
Delegate ruthlessly. Get a 2IC/COO to deal with running operations, concentrate on strategy, people, ensuring your organisation is the right shape, value add.
When I was a direct report for a CIO of a fairly large multinational (40+ countries) my boss spent most of his time on the road travelling - he had a gruelling job. He was completely hands off when to technology - although he was actually fairly technical.
And then the viva64 "book" is basically a list of open source projects with bugs in spotted by Karpov's pet static analyser. Very little of excitement to see here, just a grab bag of gotchas - pretty much like C++ itself. /runs for cover