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

Re: Committing Resources to Win32

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: Committing Resources to Win32
Date: 2003-11-10 21:39:58
Message-ID: 303E00EBDD07B943924382E153890E5434AA05@cuthbert.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
Joshua D. Drake wrote:
> aren't good enough?".  We could always use Borland or Intel.

Borland released (not sure if they still do) a C++ compiler that is free
for download (but closed source).  Borland's compiler is a pretty decent
C++ compiler, not sure how well it handles C, it does support TLS
though.  
 
> I believe that Apache 2.x is not completly threaded.. don't they use
> some kind of hybrid model?

Apache by nature has a lot more performance issues wrt threading and
process management.  Postgres is more generally I/O bound.  My
professional opinion is that for win32 performance we should be looking
at how the file system calls, especially synching, will run rather than
ipc and threading.

> Hmmm... maybe this all becomes moot if we also do connection pooling?

This would serialize all database access...IMO not worth considering
this angle.

TLS variables are supported by the Win32 API, and all C compilers for
windows support the Win32 API.  __declspec(thread) is just syntactic
sugar which automate the API TLS commands.  Converting the variable
access syntax is likely just one part of the overall move to the
threaded approach.  A win32 centric move to threading will marginalize
the port (again, IMO).

Regards,
Merlin



Responses

pgsql-hackers-win32 by date

Next:From: Andrew DunstanDate: 2003-11-10 22:10:35
Subject: Re: Committing Resources to Win32
Previous:From: Joshua D. DrakeDate: 2003-11-10 21:11:13
Subject: Re: Committing Resources to Win32

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