Nic Cope

@tnthornton very strange - your setup is almost identical to mine, but your test looks like it took 18 seconds to my 1. Only possible differences I can spot are...

For historical context, all the folks posting results here are testing against the same EKS server I used. We're definitely noticing a trend of the slowdown being on MacOS. I...

On the API server memory consumption front, I did some not very scientific tests with https://github.com/kcp-dev/kcp today and found that it appears to use about half the memory of the...

@jonnylangefeld The idea was to (casually) test multiple different clients against the same server. We all used the same EKS API server. To my knowledge everyone experiencing slowness was being...

CC @prasek

> IIRC #1770 was focused on making these CRRs more generic at the managed resource level to simplify codegen Exactly. > AFAIK composed resources benefit from this behavior as well,...

Thanks for the feedback folks. It's helpful to understand the use cases here. To summarize, I'm seeing: * **Performance degradation**. So far we've preferred trying to work with upstream to...

@ulucinar regarding https://github.com/crossplane/crossplane/issues/2869#issuecomment-1108422111, I recall we had some technical concerns with this implementation, but I unfortunately can't find them written down anywhere. One issue was how we'd handle cross-resource-references. For...

> Does it stand to reason that retrieving a list of 1000s of resources using kubectl/k8s API is always going to be slower than a list of 10s of resources,...

> This doesn't address the other issues around user experience, general bloat or highly regulated environments though. I'd love to hear more detailed experience reports from folks in these highly...