| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | hannu(at)tm(dot)ee |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: multibyte performance |
| Date: | 2001-09-27 12:30:38 |
| Message-ID: | 20010927213038L.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > With multibyte support(first column is the concurrent user, second is
> > the TPS):
> ...
> > 32 95.947363
> > 64 92.718780
> > 128 61.725883
> >
> > Witout multibyte support:
> ...
> > 32 92.283645
> > 64 86.936559
> > 128 87.584099
>
> Do you have any theory why multibyte passes non-mb at 128 ?
>
> Some subtle timing thing perhaps (or just bad luck for non-mb at 128)?
May be or may not be. I was anxious about the load module size and
thought it might stress the memory. So while running pgbench I checked
the memory usage using vmstat. However it showed no excess page
in/page out...
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haller Christoph | 2001-09-27 12:59:47 | Re: Abort transaction on duplicate key error |
| Previous Message | Haller Christoph | 2001-09-27 11:27:09 | Abort transaction on duplicate key error |