Re: [AOLSERVER] aolserver and mysql

2006-10-24 Thread Dossy Shiobara
On 2006.10.24, Derek Keller [EMAIL PROTECTED] wrote:
 i have the opportunity to use aolserver in a project but i'm stuck  
 with mysql.  i've seen very little discussion on it, so i'm wondering  
 if any of you have actually used aolserver/mysql in a production  
 environment.  i'm just concerned about the currency of the mysql  
 driver (does it handle new stuff in mysql 5), stability, general  
 performance.

It'd be nice to have a list of places where AOLserver/MySQL is used in
production.  I know that it is in use at AOL.

The current nsmysql driver is stable, but it doesn't take advantage of
any new MySQL client functionality in MySQL 5.  If that's a concern for
you, come up with a list of things you need and I'll work on
implementing support for it.

 in other words, should i bother?

Depends on what your requirements are.

-- Dossy

-- 
Dossy Shiobara  | [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on. (p. 70)


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] only one connection thread

2006-10-24 Thread Brad Chick
On Mon, 23 Oct 2006 11:06:45 -0400, Nathan Folkman [EMAIL PROTECTED] wrote:

[EMAIL PROTECTED] wrote:
 Following up on Stuart's call for clarification, can someone please send
 some out some documentation, or point us to it, where we can figure out 
how
 to use the new ns_limits/ns_pools functionality in 4.5.

 We just used 4.5 in production and aolserver was limited to 100 
ESTABLISHED
 tcp connections, no matter what we tried. We tried to change the old
 settings, changing the keepalivetimeout to 0 and messing with:

 ns_param   connsperthread
 ns_param   maxconnections
 ns_param   maxthreads

 but not matter what we had in our configuration, nothing helped us get 
any
 more simultaneous tcp connections.

 Any help would be greatly appreciated.

 Or, maybe we should just go back to 4.0.10?

 Brad


 On Thu, 10 Aug 2006 20:59:46 +0100, Stuart Children 
[EMAIL PROTECTED]
 wrote:


 Stuart Children wrote:

 Whilst playing with a new 4.5.0 build, I suddenly noticed that I was
 only getting one concurrent connection thread running - eek!

 OK, so this is an affect of the new limits code. It's more specific than
 I initially described - it's one concurrent connection per specific
 url, where I believe url actually means url+at least some headers
 (which is slightly surprising, though I can see people having a
 requirement for it both ways). Due to the lack of response, I've no idea
 whether this is the intentional default behaviour - but it would seem to
 merit a mention in the docs if so.

 Unfortunately I'm about to leave for an extended holiday, and I've been
 pretty busy with other matters in my last few days at work, so
 investigating further how the new limits/pools stuff is actually working
 (and how one is intended to use it) will have to wait. If anyone can
 fill in the gaps whilst I'm away that would be great, but I just wanted
 to let people know I probably won't be replying for three weeks...
 holiday = no computers. :)

 Cheers

 --
 Stuart


 --
 AOLserver - http://www.aolserver.com/

 To Remove yourself from this list, simply send an email to

 [EMAIL PROTECTED] with the

 body of SIGNOFF AOLSERVER in the email message. You can leave the

 Subject: field of your email blank.

 
=



 --
 AOLserver - http://www.aolserver.com/

 To Remove yourself from this list, simply send an email to 
[EMAIL PROTECTED] with the
 body of SIGNOFF AOLSERVER in the email message. You can leave the 
Subject: field of your email blank.

Any overview of the new commands can be found in the release notes:


http://aolserver.cvs.sourceforge.net/aolserver/aolserver/
RELEASE?view=markup

Your best bet is to just look at the source:

aolserver/nsd/limits.c
aolserver/nsd/pools.c

Here's also a few additional notes I had been working on, although
probably not that helpful:


  Ns pools


   From Office Wiki

Thread pools can be configured in either application code or the
AOLserver configuration. The following example will set up a thread pool
for all GET requests to /slow/* allowing only a maximum of 2 connection
threads to be allocated. Additional requests will be queued.

ns_pools set slow -maxthreads 2
ns_pools register slow server1 GET /slow/

There are a few stats commands available as well:

server1:nscp 1 ns_server threads slow
{min 0} {max 2} {current 2} {idle 0} {stopping 0}

server1:nscp 2 ns_pools list
slow default error

server1:nscp 3 ns_pools get slow



  Ns limits


   From Office Wiki

In addition to creating and registering thread pools, you can also
specify the following limits:

maxrun maxwait maxupload timeout

minthreads 0 maxthreads 2 idle 0 current 2 maxconns 2 queued 8 timeout 5



Well,

We've playing with settings like:

ns_limits set default -maxrun 999
ns_limits set default -maxwait 999
ns_pools set default -maxthreads 999
ns_pools set default -maxconns 999

ns_pools set lots -maxthreads 998
ns_pools register lots server1 GET /lasalle/

But not matter what we do, we can never get aolserver to accept more that 
100 tcp connections at once. The rest are just queued to WAIT.

We are stressing the server with a load tester and then taking a look at 
the ESTABLISHED connections.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
[EMAIL PROTECTED] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the 
Subject: field of your email blank.
=


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.