Hi Mindaugas, On Mon, Aug 27, 2012 at 04:11:59PM +0100, Mindaugas Rasiukevicius wrote: > > I am CC-ing tech-kern as well.
Good. I was not sure in which of the numerous NetBSD lists I should have posted to ;) > > On Mon, Aug 27, 2012 at 11:31:30AM +0100, Mindaugas Rasiukevicius wrote: > > > Francois Tigeot <ftig...@wolfpond.org> wrote: > > > > You're right, it's much better with a Unix socket. NetBSD follows the > > FreeBSD curve up to 24 clients (including the peak). > > Sadly, it all goes downhill from there. > > Good to know. Do you have a graph somewhere? I took some time to run an almost complete serie with NetBSD+AF_UNIX and update the pdf document (see page 3). Get it there: http://dl.wolfpond.org/benchs/Pg-benchmarks.2012-08.pdf > > Performance with 32 clients is on par with the initial 127.0.0.1 results. > > Tests with 48 or more clients are still running and will probably yield > > bad results too. > > The system is almost completely unresponsive. Just seeing 'ls' appear on > > the remote shell I use takes about 20 seconds with a long pause between > > the two letters. > > This is somewhat unexpected. Do you use some unusual configuration or just > a plain GENERIC kernel? Could you perhaps run pgbench under lockstat(8)? I'm using an almost-default installation with GENERIC. A small top(1) extract: CPU23 states: 0.0% user, 0.0% nice, 100% system, 0.0% interrupt, 0.0% idle Memory: 12G Act, 6312M Wired, 15M Exec, 12G File, 2895M Free Swap: 24G Total, 24G Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 0 root 96 0 0K 55M CPU/2 279:29 896% 896% [system] 380 ftigeot 79 0 6324M 6322M select/6 22:24 0.00% 0.00% postgres 818 ftigeot 85 0 6327M 42M select/0 0:12 0.00% 0.00% postgres -- Francois Tigeot
