Re: MySQL on an SMP system - exploiting it
From: Jerry Stuckle <jstucklex_at_attglobal.net>
Date: Tue, 23 May 2017 19:06:40 -0400
Message-ID: <og2f3g$3lo$1_at_jstuckle.eternal-september.org>
>> What exactly is your performance problem? Is it the query itself? Is
>> it the processing of that query? Or is it something else?
>>
>> You can't guarantee which core will be used when a request comes in.
>> Basically it will be whatever core is free at the time. It would be
>> quite inefficient to wait for core 2 to free up from some other
>> operation if core 1 is waiting for I/O, for instance.
>>
Date: Tue, 23 May 2017 19:06:40 -0400
Message-ID: <og2f3g$3lo$1_at_jstuckle.eternal-september.org>
On 5/23/2017 4:03 PM, bit-naughty_at_hotmail.com wrote:
> On Monday, May 22, 2017 at 6:59:42 PM UTC-5, Jerry Stuckle wrote: >
>> What exactly is your performance problem? Is it the query itself? Is
>> it the processing of that query? Or is it something else?
>>
>> You can't guarantee which core will be used when a request comes in.
>> Basically it will be whatever core is free at the time. It would be
>> quite inefficient to wait for core 2 to free up from some other
>> operation if core 1 is waiting for I/O, for instance.
>>
> > Right - so, if there are 2 cores, and core 1 is busy serving hit no. 1, then when the 2nd hit comes in, it WILL go to core 2, right? >
If that core isn't doing one of a million other possible things, yes. Your web server and MySQL are not the only things going on.
-- ================== Remove the "x" from my email address Jerry Stuckle jstucklex_at_attglobal.net ==================Received on Wed May 24 2017 - 01:06:40 CEST