> For the complete documentation index, see [llms.txt](https://doc.velneo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.velneo.com/22/velneo-vdevelop/buenas-practicas-de-programacion/buenas-practicas-de-rendimiento/buenas-practicas-base-de-datos/base-de-datos-campos-formula-vs-campos-en-disco.md).

# Campos fórmula vs campos en disco

![](/files/-M7D7C5PamFb8vkxf8ih)

## Fórmula más rápido en escritura

Los campos fórmula son más rápidos cuando estamos dando altas ya que su fórmula no tiene que calcularse, salvo que el campo se use en el contenido inicial de otros campos en una actualización. El uso de campos fórmula es interesante cuando no se trata de un dato que debamos calcular de forma constante.

## Disco más rápido en lectura

Como no es necesario volver a calcular el valor del campo, son más rápidos a la hora de leer su valor y procesarlo. Por ese motivo es preferible usar campos con persistencia en disco para valores que se leen muchas veces o campos que intervienen en el contenido inicial de otros, así se evita que la fórmula se recalcule muchas veces.


---

# 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 dynamically by asking a question.

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

```
GET https://doc.velneo.com/22/velneo-vdevelop/buenas-practicas-de-programacion/buenas-practicas-de-rendimiento/buenas-practicas-base-de-datos/base-de-datos-campos-formula-vs-campos-en-disco.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.