Re: Best Strategy for Large Number of Images

> ... I have about 2 million images ... > folder structure The "Who's On First" gazetteer with ~ 26M geojson records - using 3-number chunks subfolder structure. "Given a Who's On First ID its (relative) URI can be derived by splitting the ID in to 3-number chunks representing nested subdirectori

Re: Best Strategy for Large Number of Images

På mandag 20. desember 2021 kl. 11:29:57, skrev Estevan Rech < softr...@gmail.com >: How is this folder structure like 10,000 folders? and the backup of it, how long does it take? I recommend using SeaweedFS as blob-store, and store metadata (folder, size, filename

Re: Best Strategy for Large Number of Images

How is this folder structure like 10,000 folders? and the backup of it, how long does it take?

RE: Best Strategy for Large Number of Images

will do with the binary data that it is needed in the DB? Z From: Estevan Rech Sent: 15 December 2021 17:45 To: pgsql-general@lists.postgresql.org Subject: Best Strategy for Large Number of Images Hi, I don't currently use PostgreSQL, but I plan to migrate and I have a question abou

Re: Best Strategy for Large Number of Images

PostgreSQL, thanks to extensions, allows a third non-obvious file strategy. Since many developers when working with small images don't want to overload their solutions with the complexities of interacting with file servers, and I didn't want to store files in a database, I found and tried a third o

Re: Best Strategy for Large Number of Images

On Wed, Dec 15, 2021 at 1:12 PM Estevan Rech wrote: > > Related to this is the backup service that seems to me that in a disaster, > I can restore the database relatively quickly if it's in the database. On > the disk, I believe that the restoration is much slower and I don't think > it's reliabl

Re: Best Strategy for Large Number of Images

> I don't currently use PostgreSQL, but I plan to migrate and I have a question > about the best way/strategy for storing images. I have about 2 million images > with a growth trend of around 1 million images per year. I plan to store in bytea > format in an isolated table. Is this recommended? Is

Re: Best Strategy for Large Number of Images

I would recommend storing a link to the file rather than the file itself. Other than that, use BLOBS. I would probably recommend not storing any binary objects in a database for a variety of reasons but if you have to then bytea will work, assuming they are smaller than 2gb. Thanks, - Ben On Wed,

Re: Best Strategy for Large Number of Images

On Wed, Dec 15, 2021 at 02:45:15PM -0300, Estevan Rech wrote: > Hi, > > I don't currently use PostgreSQL, but I plan to migrate and I have a question > about the best way/strategy for storing images. I have about 2 million images > with a growth trend of around 1 million images per year. I plan to

Re: Best Strategy for Large Number of Images

Hi, when I am doing this I store the data in one postgres cluster, with some kind of id for each image , and the images in another with the id as link. The customer app is written so that it issues a dedicated http request for each image. (I use nginx to create a dedicated "path". *pro*: the images

Re: Best Strategy for Large Number of Images

On 16 Dec 2021, at 7:12, Estevan Rech wrote: > I have an application that takes pictures of items and uses them as > evidence in a report. > > These images are saved and then used to generate a report. > Once you start talking reports and evidence I think audit trail and verification a.k.a. “chai

Re: Best Strategy for Large Number of Images

Adrian, I have an application that takes pictures of items and uses them as evidence in a report. These images are saved and then used to generate a report. Each item averages 10 photos and I have about 2 million photos currently, with an average growth of 1 million photos over the next year. I

Re: Best Strategy for Large Number of Images

On 12/15/21 11:22, Estevan Rech wrote: The possibilities are known, but does anyone have experience with this scenario? It would help if you elaborated on the scenerio is? There is no questioning that you can store images in the database. The issues are what you want to do with them once they

Re: Best Strategy for Large Number of Images

On 12/15/21 12:22, Estevan Rech wrote: The possibilities are known, but does anyone have experience with this scenario? My previous employer dealt with radiology images.  These were in the file system with an image server as suggested up thread.

Re: Best Strategy for Large Number of Images

On 12/15/21 11:45 AM, Estevan Rech wrote: Hi, I don't currently use PostgreSQL, but I plan to migrate and I have a question about the best way/strategy for storing images. I have about 2 million images with a growth trend of around 1 million images per year. I plan to store in bytea format in

Re: Best Strategy for Large Number of Images

The possibilities are known, but does anyone have experience with this scenario?

Re: Best Strategy for Large Number of Images

On Wednesday, December 15, 2021, Estevan Rech wrote: > But PostgreSQL can handle it? Does it have good search performance? and is > memory usage feasible? > Images of that size won’t be stored on the main table so performance when not asking for image data should be normal. Memory is one of tho

Re: Best Strategy for Large Number of Images

On 12/15/21 10:48 AM, Estevan Rech wrote: But PostgreSQL can handle it? Does it have good search performance? and is memory usage feasible? Search on what? -- Adrian Klaver adrian.kla...@aklaver.com

Re: Best Strategy for Large Number of Images

But PostgreSQL can handle it? Does it have good search performance? and is memory usage feasible?

Re: Best Strategy for Large Number of Images

On 12/15/21 10:17 AM, Estevan Rech wrote: I think about using it inside the database to facilitate the select and generation of reports... As long as the meta data about the images is stored in the database that is still possible. -- Adrian Klaver adrian.kla...@aklaver.com

Re: Best Strategy for Large Number of Images

I think about using it inside the database to facilitate the select and generation of reports... >

Re: Best Strategy for Large Number of Images

On Wed, Dec 15, 2021 at 10:57 AM Estevan Rech wrote: > 350kb > > Em qua., 15 de dez. de 2021 às 14:50, Rob Sargent > escreveu: > >> On 12/15/21 10:45, Estevan Rech wrote: >> >> Hi, >> >> I don't currently use PostgreSQL, but I plan to migrate and I have a >> question about the best way/strategy

Re: Best Strategy for Large Number of Images

350kb Em qua., 15 de dez. de 2021 às 14:50, Rob Sargent escreveu: > On 12/15/21 10:45, Estevan Rech wrote: > > Hi, > > I don't currently use PostgreSQL, but I plan to migrate and I have a > question about the best way/strategy for storing images. I have about 2 > million images with a growth tre

Re: Best Strategy for Large Number of Images

On 12/15/21 10:45, Estevan Rech wrote: Hi, I don't currently use PostgreSQL, but I plan to migrate and I have a question about the best way/strategy for storing images. I have about 2 million images with a growth trend of around 1 million images per year. I plan to store in bytea format in an

Best Strategy for Large Number of Images

Hi, I don't currently use PostgreSQL, but I plan to migrate and I have a question about the best way/strategy for storing images. I have about 2 million images with a growth trend of around 1 million images per year. I plan to store in bytea format in an isolated table. Is this recommended? Is the