# Quão grave é "site sob carga extrema, busca desativada, tente novamente mais tarde"

**URL:** <https://meta.discourse.org/t/how-serious-is-site-is-under-extreme-load-search-is-disabled-try-again-later/125900>\
**Category:** Product Support\
**Created:** [Agosto 15, 2019, 4:39pm UTC](https://meta.discourse.org/t/how-serious-is-site-is-under-extreme-load-search-is-disabled-try-again-later/125900 "2019-08-15T16:39:10Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\
**Post date:** [Agosto 19, 2019, 11:06am UTC](https://meta.discourse.org/t/how-serious-is-site-is-under-extreme-load-search-is-disabled-try-again-later/125900/17 "2019-08-19T11:06:37Z")

</div>

Aqui está um artigo (mais ou menos relacionado a Java) que explica essa questão:

> **[N+1 problem in Hibernate & Spring Data JPA](https://www.javacodemonk.com/what-is-n-1-problem-in-hibernate-how-will-you-identify-and-solve-it-894097b9)**
>
> N+1 problem is a performance issue in Object Relational Mapping that fires multiple Select Queries in database for a single select query at application layer. Hibernate provides multiple ways to identify and prevent this problem.

---

_[View the full topic](https://meta.discourse.org/t/how-serious-is-site-is-under-extreme-load-search-is-disabled-try-again-later/125900)._