From: | Arya F <arya6000(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Hardware for writing/updating 12,000,000 rows per hour |
Date: | 2019-07-26 20:31:37 |
Message-ID: | CAFoK1ayztRr7k8ecF+m4ON4wHKD2dNZm_EnUSzSM-L4y0aQsHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 26, 2019 at 3:24 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> [ please don't top-post ]
>
> Arya F <arya6000(at)gmail(dot)com> writes:
> > On Fri, Jul 26, 2019 at 3:03 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> >> On 7/26/19 2:56 PM, Arya F wrote:
> >>> Would it be possible to achieve 12,000,000 writes/updates on a single
> >>> server? If so what kind of hardware should I be looking for?
>
> >> That's only 3,333 modifications/second. How big are your records?
>
> > As most about 2000 characters.
>
> Do you need 3K independent commits per second? Or can you batch them?
> Even just turning off synchronous_commit would move the goalposts
> pretty far in terms of the storage hardware you'll need for this.
>
> regards, tom lane
>
I think I can modify my application to do a batch update. Right now the
server has an HDD and it really can't handle a lot of updates and inserts
per second. Would changing to a regular SSD be able to easily do 3000
updates per second?
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-07-26 21:39:19 | Re: Hardware for writing/updating 12,000,000 rows per hour |
Previous Message | Tom Lane | 2019-07-26 20:24:12 | Re: Hardware for writing/updating 12,000,000 rows per hour |