# Basic advices on database layout

**URL:** <https://community.influxdata.com/t/basic-advices-on-database-layout/20198>\
**Category:** Store\
**Tags:** influxdb, schema\
**Created:** [June 2, 2021, 10:04am UTC](https://community.influxdata.com/t/basic-advices-on-database-layout/20198 "2021-06-02T10:04:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![billdangerous](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@billdangerous](https://community.influxdata.com/u/billdangerous)\
**Post date:** [June 2, 2021, 10:04am UTC](https://community.influxdata.com/t/basic-advices-on-database-layout/20198/1 "2021-06-02T10:04:25Z")

</div>

Hello,

I would like to store different metrics like temperature, pression or humidity. They are all supposed to be stored in the same bucket.

I have some difficulties to understand the differences in terms of performance/layout/good practices between having multiple measurement for each metrics such as

```
temperature value=X timestamp
humidity value=Y timestamp
pression value=Z timestamp

```

And having only one metric but multiple fields

```
meteo temperature=X,humidity=Y,pression=Z timestamp

```

What are the consequences of each choice, and what is the best choice?

Thank you in advance,  
Bill

---

<div class="post-metadata">

**Author:** ![Anaisdg](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/anaisdg/32/6401_2.png) [@Anaisdg](https://community.influxdata.com/u/Anaisdg)\
**Post date:** [June 8, 2021, 6:13pm UTC](https://community.influxdata.com/t/basic-advices-on-database-layout/20198/2 "2021-06-08T18:13:40Z")

</div>

Hello @billdangerous,  
Tags and measurements are indexed, fields are not.  
If minimizing query response time is a priority then you could separate out the fields in separate measurements or tags depending to fit common queries you’d be executing.  
If easily visualizing all data together is a priority or performing math across data is important than you might want to consider keeping it all in one measurement. Of course you can perform math across measurements but you would have to execute a join first.

The following blogs might be helpful to you:

> **[Data Layout and Schema Design Best Practices for InfluxDB](https://www.influxdata.com/blog/data-layout-and-schema-design-best-practices-for-influxdb/)**
>
> This post shows how to figure out the best data layout for InfluxDB v2, some schema design best practices, and a schema development example.

> **[InfluxDB: How to Do Joins, Math across Measurements | Blog | InfluxData](https://www.influxdata.com/blog/influxdb-how-to-do-joins-math-across-measurements/)**
>
> InfluxData has released the technical preview of Flux, and with it comes the ability to perform math across measurements.

---

<div class="post-metadata">

**Author:** ![billdangerous](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@billdangerous](https://community.influxdata.com/u/billdangerous)\
**Post date:** [June 8, 2021, 6:52pm UTC](https://community.influxdata.com/t/basic-advices-on-database-layout/20198/3 "2021-06-08T18:52:31Z")

</div>

Thank you for this clear answer.

---

<div class="post-metadata">

**Author:** ![Anaisdg](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/anaisdg/32/6401_2.png) [@Anaisdg](https://community.influxdata.com/u/Anaisdg)\
**Post date:** [June 8, 2021, 9:56pm UTC](https://community.influxdata.com/t/basic-advices-on-database-layout/20198/4 "2021-06-08T21:56:08Z")

</div>

@billdangerous of course! Thank you for your patience.