Scalable postgresql using sys_epoll

Started by Nonamealmost 22 years ago3 messages
#1Noname
anthony_barker@hotmail.com

IBM has rewritten their Domino database system to use the new
sys_epoll call available in the Linux 2.6 kernel.

Would Postgresql benefit from using this API? Is anyone looking at
this?

Anthony
http://xminc.com/mt/

#2Shachar Shemesh
psql@shemesh.biz
In reply to: Noname (#1)
Re: Scalable postgresql using sys_epoll

Anthony_Barker wrote:

IBM has rewritten their Domino database system to use the new
sys_epoll call available in the Linux 2.6 kernel.

Would Postgresql benefit from using this API? Is anyone looking at
this?

Anthony
http://xminc.com/mt/

I'm not familiar enough with the postgres internals, but is using
libevent (http://monkey.org/~provos/libevent/) an option? It uses state
triggered, rather than edge triggered, interface, and it automatically
selects the best API for the job (epoll, poll, select). I'm not sure
whether it's available for all the platforms postgres is available for.

Shachar

--
Shachar Shemesh
Lingnu Open Systems Consulting
http://www.lingnu.com/

#3Matthew Kirkwood
matthew@hairy.beasts.org
In reply to: Shachar Shemesh (#2)
Re: Scalable postgresql using sys_epoll

On Wed, 10 Mar 2004, Shachar Shemesh wrote:

IBM has rewritten their Domino database system to use the new
sys_epoll call available in the Linux 2.6 kernel.

Would Postgresql benefit from using this API? Is anyone looking at
this?

I'm not familiar enough with the postgres internals, but is using
libevent (http://monkey.org/~provos/libevent/) an option? It uses state
triggered, rather than edge triggered, interface, and it automatically
selects the best API for the job (epoll, poll, select). I'm not sure
whether it's available for all the platforms postgres is available for.

libevent is cool, but postgres uses a process-per-client
model, so the number of file descriptors of active interest
to a backend at any given time is low.

Matthew.