helm安装signoz，signoz query service扩展副本数，造成登录反复创建用户，这个问题可以解决吗？signoz支持拓展各query service等服务的副本数吗？

Multiple instances of query-service is not supported. It should be okay to increase pod replicas for other components except otel-collector-metrics.

query service服务不支持多副本，这样是否会成为整个signoz集群的性能瓶颈，如果数据量大，query service单副本能支撑吗？

Query-service is only responsible for getting the data, it should be able to handle querying of large data. You can scale it up vertically meaning you can increase the resources allotted to query-service for more scale. On the other hand, otel-collectors are responsible for data ingestion and that can be scaled as per the need.

因此signoz查询历史数据比较慢的话，可以选择的操作就是增加cpu内存资源吗？还有其他方法吗？

By default, there is no resource limit. It can take up all of the resource in the Kubernetes node. You could set a resource limit for query-service, if needed:

queryService:
  resources:
    requests:
      cpu: 100m
      memory: 100Mi
    limits:
      cpu: 2
      memory: 2Gi