| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, vadim4o(at)email(dot)com |
| Subject: | Re: Re: beta5 ... |
| Date: | 2001-02-17 17:30:02 |
| Message-ID: | 4145.982431002@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The Hermit Hacker <scrappy(at)hub(dot)org> writes:
>> The easy fix is to just set the delay to zero. Looks like that will fix
>> most of the problem.
> Except that Vadim had a reason for setting it to 5,
He claimed to have seen better performance with a nonzero delay.
So far none of the rest of us have been able to duplicate that.
Perhaps he was using a machine where a 5-microsecond select() delay
actually is 5 microseconds? If so, he's the outlier, not the
rest of us ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-02-17 18:05:53 | WAL and commit_delay |
| Previous Message | Tom Lane | 2001-02-17 17:26:31 | Re: Microsecond sleeps with select() |