Pagesize for large-objects (ONLY) database.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,
I am planning to have a postgres database for large object storage. I believe that with version 9.0, the 'world readable' issue with pg_largeobject is resolved and we can now control at object level- which users can read/write what objects.

Streaming performance is an issue and hence will need to increase the PAGE SIZE (BLCKSZ ) to ensure access is sequential. Does anyone have recommendation on a BLCKSZ I can start with.
There will be lot of reads,updates,inserts,deletes of the objects. Also any ideas on how big of an issue fragmentation can be and how can it be contained ?

About 70% of the objects will be less than 1MB, about 25% upto 10MB and rest 5% or so may be larger than 10MB.

Metadata management is also important so just a distributed filesystem (rather than database) is not viable. Any other suggestions are welcome.

Thank you! - AJ


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux