Open richard-cox opened 1 year ago
Some of the backend changes have already been implemented in 2.7.2
Anything marked as
Development note
are implementation details for this issue and are candidates to spin out
Some are incoming in 2.7 Q2
Some that we would like for 2.7 Q2 but are not blocking (in order of importance)
In addition we need to consider more advanced ways to search
The backend will not support sorting/filtering on 'calculated' fields e.g. current model getters. For the first iteration we should concentrate on badly performing lists that don't need them, this does include all workload types and secrets.
I wanted to say this 2 years ago, but I decided to wait and give Rancher time to improve. I can't help but notice this issue is a year old. Still, in 2024 Rancher's performance makes the product completely unusable, while alternative tools are fast and snappy.
I quit using Rancher because it's soooo slow. It's hogging 4 GB memory and 4 CPUs on a brand new cluster. It's been doing this ever since rancher 2.6 and there seems to be no improvements.
I don't understand how alternative tools can be so fast, while the rancher dashboard just freezes all the time because the rancher server CPU and Memory get maxed out. Makes no sense to me.
1 user, 1 cluster, 4 gb ram, 4 cpus and it's still not enough, and it's been this way for years. It's the one issue that's forced me to look for alternatives.
The rancher product feature set is great, but I really wish I could say the same about its performance.
@clayrisser This is a year old, and I can empathise with the frustration you've experienced. We are very actively working on a solution though (see linked issues and their prs for UI progress). Unfortunately API side hit a road block which has delayed things a bit. I'm happy to say though that we are targeting a tech preview of the feature in 2.9.0.
In addition 2.9.0 contains many UI performance improvements that assist both memory and CPU usage. It's worth giving that a try when released.
I will try again with 2.9.0, but if it requires running a large server, (more than 4 CPU) it's just not worth it.
I'm going to assume rancher works well for very large deployments that have resources to throw at it, but small deployments can't justify too many resources for it.
2.9 cut off
2.10 cut off (WIP)
catalog/load
Backend Issues (not complete list)
Related