Mutliple small Raw-Span PVCs instead of one large PVC

FYI, I removed the customer name, as this idea was initially submitted as world readable (visible to all)

Hi Kurtulus,

can you use S3-comptabile object storage, such as minio https://www.ibm.com/docs/en/instana-observability/current?topic=openshift-api-reference#s3config for rawSpans? This is what SaaS and other large customers are using to scale.

After discussing with the team, sharding into two or multiple PVCs is not feasible on the application level (the performance gain you seek would be likely be removed by the added complexity in the application). I will therefore close this AHA idea and suggest you look at object storage, which should not have scaling limits.

Best,
Hubert

Hi Hubert,

I don't know the exact details but for example, they told us that metadata of cephfs storage increase when the PVC size increase, and as a result metadata search time also increases which leads to performance bottlenecks. Instead of this, small-size PVCs like 1TB x 8 or 2TB x 4 perform better.

Thank you.

Hi Hubert,

The remediation comes from ISBANK storage team , we want more flexible on the storage side for instana,we can't request 2*4TB disk from yaml,for now we can only commit storage: 3Ti at the operator yaml , our need is to write multiple pvc on the yaml file of operator because for now we have +1000 agent and we really need to expand raw-span pvc in a short time.

Regards

 storageConfigs:
 rawSpans:
 pvcConfig:
 resources:
 requests:
 storage: 3Ti
 storageClassName: cephfs-retain

Hi Doruk,

thanks for your idea to Instana Self-Hosted. Can you give more context how 2*4TB PVCs are more performant then 1*8TB PVC for your customer? For cloud providers it is usually the opposite, you need to request (and pay) for larger PVCs to get more performance.