700+ (contacts). Log around lookup, when beam.smp eats CPU, is attached. It looks to me that there are a lot of requests for that lookup - perharps lowering those to one request will solve the problem?
700+ (contacts). Log around lookup, when beam.smp eats CPU, is attached. It looks to me that there are a lot of requests for that lookup - perharps lowering those to one request will solve the problem?