Moreover, what's an efficient way to deploy a GCF solution given the requirement for multiple related functions? (And given that each deployment step is fairly slow - 10's of seconds)

This sounds like a straightforward question, but I can't find a straight answer with exactly what to do. I've read a few related answers on SO, but they aren't very clear.

The Google documentation here mentions exporting "one or more functions": <https://cloud.google.com/functions/docs/writing/>

But when it comes time to deploy, the CLI command explicitly only deploys one function as far as I can tell: `gcloud beta functions deploy OneFunctionNameHere`.

What am I missing?
If I have several related functions in one index.js, surely I don't need several slow `gcloud beta functions deploy` commands?
(Or maybe I do so that I get independent reporting for each one???)

I'm guessing one of these might be the answer, but I'm really not sure:

1. Push/deploy once from local source into a GCP bucket, then deploy from that bucket for the other functions? (Faster?)
2. Extend the access URL like ".../MyFunction/SomeSubFunction" and use request.params to route to the right response-generating code. (There are npm packages for that..)
3. Run multiple deploys in *parallel* so that 'time to deploy' isn't a big issue (bandwidth allowing...)

Thanks for any wisdom for a better solution.