This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Performance and Scalability #8403
Comments
|
Hi @Tommolo , thanks for opening the issue. What version of Kiali are you using? |
|
I'm using kiali v2.0.0 |
|
This probably should not be a separate issue - we already have an epic on this with related issues, unless you have a specific issue that you can specify what is causing the slowdown. So I would recommend participating in the already existing epic/issues for performance related tasks. Please see: |
|
As for this question:
See the one link above with the test doc page - that's what it is geared to answer |
|
@jmazzitelli at least it's another helpful data point. @Tommolo for performance issues it's also helpful to include as much context as you can to help us get an idea of where the bottleneck is. You've included how many workloads/services this is for which is very helpful. How many namespaces are selected on the graph page? Roughly how many istio configuration objects (DestinationRules, VirtualService, etc.) are there? For graph generation it could be rendering the graph (UI), generating the graph (Kiali backend), prometheus, or the connection between your browser and the Kiali API. We're actively working on making these issues easier to diagnose and report. See: #8345. In the meantime, Kiali emits some metrics about graph generation. You can query for There's not really a magic configuration knob to make performance better. You can try scaling Kiali up (more cpu/mem) or scaling up Prometheus but without knowing exactly where the bottleneck is I can't guarantee that will help. |
|
I’m also having issues with this and had a couple of questions:
|
That would seem likely, though I can't give you a reason why. I don't think we have had any users up to this point with 10 clusters in the mesh (none that told us about it anyway).
No, the installation mechanism shouldn't make a difference when looking at performance of the server. |
|
I'd also suggest always using the most recent version of Kiali that is compatible with your Istio version. Also, Kiali performance is very tied to Prometheus query performance, so you may also want to look at https://kiali.io/docs/configuration/p8s-jaeger-grafana/prometheus/#prometheus-tuning. |
|
There is no specific issue here, and nothing we can really action on. I'm going to convert this to a discussion... |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'm trying to use Kiali in an environment where I have a namespace with a high number of deployments and services (around 320 deployments and 200 services). I've noticed that Kiali is very slow when loading the traffic graph. Is there a way to reduce the loading time?
The text was updated successfully, but these errors were encountered: