On Tue, Apr 5, 2011 at 5:50 AM, Arjen Lentz wrote:
> On 04/04/2011, at 11:55 PM, MARK CALLAGHAN wrote:
>>
>> And then because this is Sun CoolThread hardware, each connection runs
>> on really, really slow CPUs. And 48 threads running concurrently will
>> get a lot of mutex contention from MySQL s
Hi Mark
On 04/04/2011, at 11:55 PM, MARK CALLAGHAN wrote:
And then because this is Sun CoolThread hardware, each connection runs
on really, really slow CPUs. And 48 threads running concurrently will
get a lot of mutex contention from MySQL so maybe running 4 copies of
mysqld with each instance l
Hi Mark,
It makes sense.
Thanks.
Alex
Em 04/04/2011, às 10:55, MARK CALLAGHAN escreveu:
And then because this is Sun CoolThread hardware, each connection runs
on really, really slow CPUs. And 48 threads running concurrently will
get a lot of mutex contention from MySQL so m
And then because this is Sun CoolThread hardware, each connection runs
on really, really slow CPUs. And 48 threads running concurrently will
get a lot of mutex contention from MySQL so maybe running 4 copies of
mysqld with each instance locked down to 12 CoolThread CPUs will help.
On Sun, Apr 3, 2
Alexandre Almeida writes:
> As far as I can see MariaDB stay locked/running on a single
> virtual CPU and MariaDB doesn't take advantage of CoolThread/CMT
> technologies, I mean it can not run on more than one virtual CPU same
> time. Result: poor performance.
>
> Anybody knows if
Hi all,
I am installing MariaDB on a server Sun/Oracle T5140 with CoolThread/
CMT technology.
This server has two physical Sparc CPU with 48 1165MHZ virtual
processors each. However, it's look like that MariaDB is performing
much better on my MacBook Pro when compared against this server
6 matches
Mail list logo
