# Huge amount of storage transactions

**URL:** https://meta.discourse.org/t/huge-amount-of-storage-transactions/151922
**Category:** Self-hosting
**Created:** [19 mei 2020 om 09:53 UTC](https://meta.discourse.org/t/huge-amount-of-storage-transactions/151922 "2020-05-19T09:53:59Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![klopsknoedel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/klopsknoedel/32/194126_2.png) [@klopsknoedel](https://meta.discourse.org/u/klopsknoedel)
#### Post date: [22 mei 2020 om 21:18 UTC](https://meta.discourse.org/t/huge-amount-of-storage-transactions/151922/11 "2020-05-22T21:18:03Z")

</div>

Thanks for clarification and your advice. indeed SMB can be very slow if it comes to accessing a lot of files. Most of the time it makes no difference as frequently accessed files got cached by nginx (we frequently apply the changes made to the discourse nginx sample config).  
But when it comes to those peeks the performance drops.

We’re looking for other storage solutions for some time now. Using an external s3 (compatible) storage ~~would~~ may break parts of our security concept. Every instance/service involved (db, vm, storage, …) is bound to a private network and inaccessible from public internet. All public traffic is managed by an Azure Application Gateway.  
Unfortunately Azure Blob Storage is not S3 compatible but we may should invest some time making use of it.  
Current possible solutions are the [Discourse Blob Storage plugin](https://meta.discourse.org/t/azure-blob-storage-plugin/79392) or using [blobfuse](https://github.com/azure/azure-storage-fuse) directly inside the container.

Anyway. Thanks for your time and help. Is there a reason why upload size will be checked daily and is there a way to turn that off?

Kind Regards

---

_[View the full topic](https://meta.discourse.org/t/huge-amount-of-storage-transactions/151922)._
