Hello,
I developed a small application based on the GRPC example of the asylo repo, but even though it's fairly trivial it's not really usable because the moment it starts, it immediately spawns 4 threads that each consume 100% of a core. I am running everything using the `buildenv-v0.3.4` Docker image.
I tried passing a `ResourceQuota` object to the `ServerBuilder` object to reduce the threads to 1 but it seems to be ignored because I see again 4 threads consuming all my cycles. I tried running just the Asylo GRPC example and I saw that it has the exact same issue and the `ResourceQuota` does not make any difference in this case either. I tried running the C++ GRPC example from the GRPC repo in github and it run without any issue and without requiring any significant number of cycles, so I am pretty sure that this is an issue with Asylo. I tried looking around at the Asylo GRPC additions but nothing seems off and I haven't done any serious work in C++ so I am shit at debugging the problem directly.
Does anyone have experience with this problem and if yes, how did you solve it?
Cheers,
Pavlos