| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Ciprian Dorin Craciun <ciprian(dot)craciun(at)gmail(dot)com> |
| Cc: | Shane Ambler <pgsql(at)sheeky(dot)biz>, Diego Schulz <dschulz(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Using Postgres to store high volume streams of sensor readings |
| Date: | 2008-11-22 22:26:27 |
| Message-ID: | 20081122222627.GD3813@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ciprian Dorin Craciun escribió:
> I've tested also Sqlite3 and it has the same behavior as
> Postgres... Meaning at beginning it goes really nice 20k inserts,
> drops to about 10k inserts, but after a few million records, the HDD
> led starts to blink non-stop, and then it drops to unde 1k....
The problem is, most likely, on updating the indexes. Heap inserts
should always take more or less the same time, but index insertion
requires walking down the index struct for each insert, and the path to
walk gets larger the more data you have.
Postgres does not have bulk index insert, which could perhaps get you a
huge performance improvement.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-11-22 22:32:32 | Re: Using Postgres to store high volume streams of sensor readings |
| Previous Message | David Wilson | 2008-11-22 22:16:49 | Re: Using Postgres to store high volume streams of sensor readings |