Re: autoprewarm_dump_now

Hello!

I have made a patch, now we can allocate more than 1 GB of memory for the
autoprewarm_dump_now function.

Best regards,

Daria Shanina

пт, 4 апр. 2025 г. в 19:36, Robert Haas <robertmhaas(at)gmail(dot)com>:

> On Fri, Apr 4, 2025 at 12:17 PM Melanie Plageman
> <melanieplageman(at)gmail(dot)com> wrote:
> > Unrelated to this problem, but I wondered why autoprewarm doesn''t
> > launch background workers for each database simultaneously instead of
> > waiting for each one to finish a db before moving onto the next one.
> > Is it simply to limit the number of bgworkers taking up resources?
>
> That's probably part of it, but also (1) a system that allowed for
> multiple workers would be somewhat more complex to implement and (2)
> I'm not sure how beneficial it would be. We go to some trouble to make
> the I/O as sequential as possible, and this would detract from that. I
> also don't know how long prewarming normally takes -- if it's fast
> enough already, then maybe this doesn't matter. But if somebody is
> having a problem with autoprewarm being slow and wants to implement a
> multi-worker system to make it faster, cool.
>
> --
> Robert Haas
> EDB: http://www.enterprisedb.com
>