From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Adrian Grucza <adrian(dot)grucza(at)iress(dot)com> |
Cc: | pgsql-odbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: [PATCH] Using mimalloc to improve performance and reduce memory allocation lock contention |
Date: | 2024-03-25 10:59:25 |
Message-ID: | CADK3HHLB15KyoC47Z25kXiyYEPD5CwYTNRjmN9xkrfiD1D6Ojw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Mon, 25 Mar 2024 at 01:42, Adrian Grucza <adrian(dot)grucza(at)iress(dot)com> wrote:
> Hi,
>
> We have a multi-threaded Windows application that was experiencing delays
> due to high lock contention in memory allocations from the PostgreSQL ODBC
> driver. We tried modifying the driver to use mimalloc
> <https://github.com/microsoft/mimalloc>, which is a memory allocator with
> better performance characteristics. After deploying this change, the delays
> due to lock contention disappeared. It has been running on thousands of our
> production deployments for 9 months without issue.
>
> I've created this pull request
> <https://github.com/postgresql-interfaces/psqlodbc/pull/6> so that others
> can benefit from this change by building the driver with the _MIMALLOC_
> symbol defined and linking to the mimalloc library.
>
> In my patch, the usage of mimalloc is off by default, so it should be safe
> to merge. But I'd like to get people's thoughts on whether it should be
> enabled by default so that people can benefit from this change without
> having to build the driver themselves.
>
Cool,
Thanks, I will have a look
Dave
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2024-03-28 09:47:48 | Re: question on PostgreSQL ODBC driver |
Previous Message | Adrian Grucza | 2024-03-25 05:41:40 | [PATCH] Using mimalloc to improve performance and reduce memory allocation lock contention |