postgresql-interfaces/psqlodbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed
From: abhi-555 (@abhi-555) <[email protected]>
To: postgresql-interfaces/psqlodbc <[email protected]>
Subject: Re: [postgresql-interfaces/psqlodbc] issue #88: Poor performance of psqlodbc while executing ODBC array operations from TPCC load
Date: Mon, 10 Feb 2025 15:11:57 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

[Standalones.zip](https://github.com/user-attachments/files/18735771/Standalones.zip)

I have attached a standalone for batch_insert and batch_update in Standalones.zip . We are using these to detect the time taken and rate of records processed during batch insert and update simultaneously. The DDL of the table used is present in the CPP files.

We have the below summary where we have performed a comparison between the psqlodbc driver and a third party postgres driver. We are seeing significantly lower rates of processing in batch insert and update using psqlodbc driver. 

Summary of comparison

Records per batch 10000
Number of batches 1

Insert Rates
psqlodbc driver : 46190.0 records/sec
third party postgres driver : 163041.5 records/sec

Update Rates
psqlodbc driver : 26060.5 records/sec
third party postgres driver : 59786.5 records/sec

Would request you to provide us some fix which can help improve this performance
































































view thread (10+ messages)  latest in thread

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://postgresql-interfaces/psqlodbc
  Cc: [email protected], [email protected]
  Subject: Re: [postgresql-interfaces/psqlodbc] issue #88: Poor performance of psqlodbc while executing ODBC array operations from TPCC load
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox