Skip site navigation (1) Skip section navigation (2)

Re: Reasoning behind process instead of thread based

From: Thomas Hallgren <thhal(at)mailblocks(dot)com>
To: Marco Colombo <marco(at)esi(dot)it>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Reasoning behind process instead of thread based
Date: 2004-10-28 19:07:28
Message-ID: thhal-0GtxcAh273kArq7MP0ryb6tI0hJKd0L@mailblocks.com (view raw or flat)
Thread:
Lists: pgsql-general
Marco,

> I mean an entirely event driven server. The trickiest part is to handle
> N-way. On 1-way, it's quite a clear and well-defined model.

You need to clarify this a bit.

You say that the scheduler is in user-space, yet there's only one thread 
per process and one process per CPU. You state that instead of threads, 
you want it to be completely event driven. In essence that would mean 
serving one event per CPU from start to end at any given time. What is 
an event in this case? Where did it come from? How will this system 
serve concurrent users?

Regards,
Thomas Hallgren



In response to

pgsql-general by date

Next:From: Sally SallyDate: 2004-10-28 19:13:14
Subject: Re: primary key and existing unique fields
Previous:From: Bruno Wolff IIIDate: 2004-10-28 17:44:00
Subject: Re: primary key and existing unique fields

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group