eBay once developed a patch for pooled threads, on top of 5.0, to resolve this
kind of issue so they can support 10k+ sessions(massive amount of application
need to talk to those mysql).
Not sure whether they are merged into main version though.
Best regards
Zhuchao
在 2011-4-14，17:59，Rei
Am 14.04.2011 11:50, schrieb Johan De Meersman:
> - Original Message -
>> From: "Reindl Harald"
>>
>> even if you have enough memory why will you throw it away for a
>> unusual connection count instead use the RAm for innodb-buffer-pool,
>> query-cache, key-buffers?
>
> Maybe the applicat
- Original Message -
> From: "Reindl Harald"
>
> even if you have enough memory why will you throw it away for a
> unusual connection count instead use the RAm for innodb-buffer-pool,
> query-cache, key-buffers?
Maybe the application doesn't have support for connection pooling and can't
net
> To: mysql@lists.mysql.com
> Subject: Re: Practical connection limits MySQL 5.1/5.5
>
>
> Am 13.04.2011 23:50, schrieb Jeff Lee:
> > Hey All,
> >
> > Can anyone provide some guidance as to what the practical connection limits
> > to MySQL 5.1/5.5 are
Am 13.04.2011 23:50, schrieb Jeff Lee:
> Hey All,
>
> Can anyone provide some guidance as to what the practical connection limits
> to MySQL 5.1/5.5 are under linux?
>
> We're running a ruby on rails application that establishes 50 to 100
> connections to our database upon startup resulting in a
Hey All,
Can anyone provide some guidance as to what the practical connection limits
to MySQL 5.1/5.5 are under linux?
We're running a ruby on rails application that establishes 50 to 100
connections to our database upon startup resulting in around 1,000
persistent db connections. I've been told
