| From: | Ivan Voras <ivoras(at)freebsd(dot)org> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] MIT benchmarks pgsql multicore (up to 48)performance |
| Date: | 2010-10-06 22:31:19 |
| Message-ID: | i8itbn$kre$1@dough.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 10/04/10 20:49, Josh Berkus wrote:
>> The other major bottleneck they ran into was a kernel one: reading from
>> the heap file requires a couple lseek operations, and Linux acquires a
>> mutex on the inode to do that. The proper place to fix this is
>> certainly in the kernel but it may be possible to work around in
>> Postgres.
>
> Or we could complain to Kernel.org. They've been fairly responsive in
> the past. Too bad this didn't get posted earlier; I just got back from
> LinuxCon.
>
> So you know someone who can speak technically to this issue? I can put
> them in touch with the Linux geeks in charge of that part of the kernel
> code.
Hmmm... lseek? As in "lseek() then read() or write()" idiom? It AFAIK
cannot be fixed since you're modifying the global "strean position"
variable and something has got to lock that.
OTOH, pread() / pwrite() don't have to do that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jon Nelson | 2010-10-06 22:34:20 | Re: [HACKERS] MIT benchmarks pgsql multicore (up to 48)performance |
| Previous Message | Alvaro Herrera | 2010-10-06 21:21:06 | Re: security hook on table creation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jon Nelson | 2010-10-06 22:34:20 | Re: [HACKERS] MIT benchmarks pgsql multicore (up to 48)performance |
| Previous Message | Merlin Moncure | 2010-10-06 14:49:53 | Re: Runtime dependency from size of a bytea field |