Is there a maximum size limit for individual objects/records when running Weaviate on Azure?

Support
1

  1. Do these limits differ from standard Weaviate deployments on other platforms?

  2. Are there any Azure-specific configurations I should be aware of to optimize for larger record sizes?

  3. How does Azure’s infrastructure affect Weaviate’s performance with large records compared to other deployment options?

2

hi @Anushka_Sonawane !!

The only limit is about resource limit of your cluster.

The only specific configuration to deploy a k8s Weaviate Cluster in Azure is using disk.csi.azure, and not file.csi.azure.com, as stated here:

Let me know if this helps!

3

Hi @DudaNogueira, thanks for the information. Could you please provide a clearer explanation or a more detailed overview of the topic?

4

Hi!

Jut like in AWS, you can’t use a file system storage (NFS based, for example)

On those situation, the file can get corrupted.

So, in Azure, for example, you must use disk.csi.azure.com

Let me know if this helps!