Re: performance for high-volume log insertion
| От | Stephen Frost |
|---|---|
| Тема | Re: performance for high-volume log insertion |
| Дата | |
| Msg-id | 20090422203703.GH8123@tamriel.snowman.net обсуждение исходный текст |
| Ответ на | Re: performance for high-volume log insertion (Glenn Maynard <glennfmaynard@gmail.com>) |
| Ответы |
Re: performance for high-volume log insertion
Re: performance for high-volume log insertion |
| Список | pgsql-performance |
Glenn,
* Glenn Maynard (glennfmaynard@gmail.com) wrote:
> This is all well-known, covered information, but perhaps some numbers
> will help drive this home. 40000 inserts into a single-column,
> unindexed table; with predictable results:
Thanks for doing the work. I had been intending to but hadn't gotten to
it yet.
> separate inserts, no transaction: 21.21s
> separate inserts, same transaction: 1.89s
> 40 inserts, 100 rows/insert: 0.18s
> one 40000-value insert: 0.16s
> 40 prepared inserts, 100 rows/insert: 0.15s
> COPY (text): 0.10s
> COPY (binary): 0.10s
What about 40000 individual prepared inserts? Just curious about it.
Also, kind of suprised about COPY text vs. binary. What was the data
type in the table..? If text, that makes sense, if it was an integer or
something else, I'm kind of suprised.
Thanks,
Stephen
Вложения
В списке pgsql-performance по дате отправления: