> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/operations/deployment/deployment-guide/troubleshooting-section/performance-issues-in-environments.md).

# Performance Issues in Environments

This document explains how to troubleshoot performance issues in the environments.

### Symptoms <a href="#symptoms" id="symptoms"></a>

Consider the following scenario:

1. When accessing any UI in the OpenG2P environment, pages may load slowly when clicking different buttons to view records.
2. When using `curl` or `ping` on the URL, responses may not be immediate.

### Cause

1. One of the nodes in your Kubernetes cluster may have network-related issues or may not be reachable by other nodes within the network.
2. You might have missed updating the Nginx upstream configuration after adding or removing a node in your Kubernetes cluster.

### Solution <a href="#solution" id="solution"></a>

1. Ping all your Kubernetes nodes from the Nginx node to identify any of that are not reachable. If you find any unreachable nodes, restart them and try pinging again.
2. Whenever you add or remove a node in your Nginx upstream configuration file, make sure to keep it updated.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/operations/deployment/deployment-guide/troubleshooting-section/performance-issues-in-environments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.