# Increasing EHRbase Storage Limit for Large Sensor Data

**Category:** [Implementation](https://discourse.openehr.org/c/implem/39)
**Created:** 2024-09-19 07:36 UTC
**Views:** 52
**Replies:** 1
**URL:** https://discourse.openehr.org/t/increasing-ehrbase-storage-limit-for-large-sensor-data/5735

---

## Post #1 by @RUTUJA_GODGHATE



I am  using EHRbase to store and manage large volumes of sensor data . I set up EHRbase using the [GitHub repository](https://github.com/ehrbase/ehrbase) as a reference. However, the current configuration seems insufficient to handle the data size, and I need guidance on increasing the storage capacity and optimizing performance in EHRbase. Specifically, I would appreciate advice on adjusting PostgreSQL settings, application configuration (e.g., cache, threads), and handling large data submissions efficiently. Any recommendations would be highly appreciated.

---

## Post #2 by @linforest

Personal guess: Additional streaming/ingestion layer between the source and the pg backend?  But I have no experience on this topic.

Related:
* [End-to-end workloads with FHIR-based protected health information (PHI) store - Microsoft Cloud for Healthcare reference architecture | Microsoft Learn](https://learn.microsoft.com/en-us/industry/healthcare/architecture/fhir-workloads)
* [Overview of the MedTech service FHIR destination mapping - Azure Health Data Services | Microsoft Learn](https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/overview-of-fhir-destination-mapping)
* [How Amazon IoT works - Amazon IoT Core](https://docs.amazonaws.cn/en_us/iot/latest/developerguide/aws-iot-how-it-works.html)

---


**Canonical:** https://discourse.openehr.org/t/increasing-ehrbase-storage-limit-for-large-sensor-data/5735
**Original content:** https://discourse.openehr.org/t/increasing-ehrbase-storage-limit-for-large-sensor-data/5735