# Do we need to care about performance issues?

Picture a developer on a laptop plugging away at the code for a site. As he is testing out the site, everything is snappy. The occasional rebuild process when he makes some minor changes is even happening in only a few seconds. Why would have a reason to stop and think that his new web app is going to be so slow that it will be nearly unusable?

The difference between the development environment and the actual user experience brings to mind the saying attributed to about everyone (Yogi Berra, Albert Einstein, Richard Feynman, Benjamin Brewster, etc.):

> In theory there is no difference between theory and practice, while in practice there is.

So what is the difference between the theory of a developer and the practice of a user? Here a few items we will cover in more depth at a later time.

* Processor performance - Developers use high-performance desktops or laptops while most people use lower powered computers or a mobile device.
* Bandwidth - Running a server on your local machine and accessing it without even going over the network is incredibly fast and makes it easy to ignore that most people will use an internet connection often one that is not particularly fast.
* Data size - When developing an application you don't generally create enough sample data to represent the large data sets that some clients use.
* Load - If you have a large number of visitors to your site your server(s) will experience drastically different loading on bandwidth, processing power, memory usage, etc. then it does when a single developer can hope to provide.

&#x20;


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.jedjs.com/why-do-we-care-about-performance-issue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
