On Sat, 29 Sep 2007 03:24:17 +0200, Alex Woick <[EMAIL PROTECTED]> wrote:
processing has ground down to really slow. I'm seeing
some incredibly long queries now in my slow-query log,
such as:
>>> Try an "optimize table " for each of the sa
>>> tables. You just filled the database f
processing has ground down to really slow. I'm seeing
some incredibly long queries now in my slow-query log,
such as:
Try an "optimize table " for each of the sa
tables. You just filled the database from scratch, so
perhaps the counters/statistics do not reflect the actual
value distribution yet
> On Fri, 28 Sep 2007 at 21:57 +0300, [EMAIL PROTECTED]
> confabulated:
>
>>
>> Optimize table does not work with InnoDB.
>
> Are you sure? An excerpt from the MySQL 5.0 documentation
> found here:
>
May be old information what I told. I tried and no errors from optimize table
with InnoDB t
On Fri, 28 Sep 2007 at 21:57 +0300, [EMAIL PROTECTED] confabulated:
Micah Anderson schrieb am 27.09.2007 02:20:
processing has ground down to really slow. I'm seeing
some incredibly long queries now in my slow-query log,
such as:
Try an "optimize table " for each of the sa
tables. You just f
> Micah Anderson schrieb am 27.09.2007 02:20:
>
>> processing has ground down to really slow. I'm seeing
>> some incredibly long queries now in my slow-query log,
>> such as:
>
> Try an "optimize table " for each of the sa
> tables. You just filled the database from scratch, so
> perhaps the cou
processing has ground down to really slow. I'm seeing some incredibly
long queries now in my slow-query log, such as:
Try an "optimize table " for each of the sa tables. You just
filled the database from scratch, so perhaps the counters/statistics do not
reflect the actual value distribution y
* Alex Woick <[EMAIL PROTECTED]> [070927 02:14]:
> Micah Anderson schrieb am 27.09.2007 02:20:
>
>> processing has ground down to really slow. I'm seeing some incredibly
>> long queries now in my slow-query log, such as:
>
> Try an "optimize table " for each of the sa tables. You just
> filled the
* Michael Parker <[EMAIL PROTECTED]> [070926 21:14]:
> micah wrote:
> > On Wed, 26 Sep 2007 17:54:05 -0700, John D. Hardin wrote:
> >
> >> On Wed, 26 Sep 2007, Micah Anderson wrote:
> >>
> >>> SELECT count(*)
> >>>FROM bayes_token
> >>> WHERE id = '4'
> >>>
On Thu, 27 Sep 2007, Henrik Krohns wrote:
> mysql> SELECT count(*) FROM bayes_token WHERE id = '1' AND (1190870335 -
> atime) > 345600;
> +--+
> | count(*) |
> +--+
> | 1710591 |
> +--+
> 1 row in set (5.69 sec)
>
> mysql> SELECT count(*) FROM bayes_token WHERE id = '1'
Micah Anderson schrieb am 27.09.2007 02:20:
processing has ground down to really slow. I'm seeing some incredibly
long queries now in my slow-query log, such as:
Try an "optimize table " for each of the sa tables. You just
filled the database from scratch, so perhaps the counters/statistics d
> > >> >> SELECT count(*)
> > >> >>FROM bayes_token
> > >> >> WHERE id = '4'
> > >> >> AND ('1190846660' - atime) > '345600';
> > >> > Who the hell wrote *that* query? Is MySQL smart enough to rearrange
> > >> > that equation to give an indexable compar
On Thu, 27 Sep 2007 08:22:31 +0300, Henrik Krohns wrote:
> On Thu, Sep 27, 2007 at 05:11:09AM +, micah wrote:
>> On Thu, 27 Sep 2007 07:48:02 +0300, Henrik Krohns wrote:
>>
>> > On Thu, Sep 27, 2007 at 03:27:51AM +, micah wrote:
>> >> On Wed, 26 Sep 2007 17:54:05 -0700, John D. Hardin wro
On Thu, 27 Sep 2007 05:11:09 +, micah wrote:
> On Thu, 27 Sep 2007 07:48:02 +0300, Henrik Krohns wrote:
>
>> On Thu, Sep 27, 2007 at 03:27:51AM +, micah wrote:
>>> On Wed, 26 Sep 2007 17:54:05 -0700, John D. Hardin wrote:
>>>
>>> > On Wed, 26 Sep 2007, Micah Anderson wrote:
>>> >
>>> >>
On Thu, 27 Sep 2007 07:48:02 +0300, Henrik Krohns wrote:
> On Thu, Sep 27, 2007 at 03:27:51AM +, micah wrote:
>> On Wed, 26 Sep 2007 17:54:05 -0700, John D. Hardin wrote:
>>
>> > On Wed, 26 Sep 2007, Micah Anderson wrote:
>> >
>> >> SELECT count(*)
>> >>FROM bayes_token
>> >>
micah wrote:
> On Wed, 26 Sep 2007 17:54:05 -0700, John D. Hardin wrote:
>
>> On Wed, 26 Sep 2007, Micah Anderson wrote:
>>
>>> SELECT count(*)
>>>FROM bayes_token
>>> WHERE id = '4'
>>> AND ('1190846660' - atime) > '345600';
>> Who the hell wrote *tha
On Wed, 26 Sep 2007 17:54:05 -0700, John D. Hardin wrote:
> On Wed, 26 Sep 2007, Micah Anderson wrote:
>
>> SELECT count(*)
>>FROM bayes_token
>> WHERE id = '4'
>> AND ('1190846660' - atime) > '345600';
>
> Who the hell wrote *that* query? Is MySQL s
On Wed, 26 Sep 2007, Micah Anderson wrote:
> SELECT count(*)
>FROM bayes_token
> WHERE id = '4'
> AND ('1190846660' - atime) > '345600';
Who the hell wrote *that* query? Is MySQL smart enough to rearrange
that equation to give an indexable comparison
I was having problems with scalability with my bayes DB, so I read up on
the mailing list and found that it was recommended to switch to the
innodb storage engine because of the row-level locking (versus the
table-level locking that comes with MyISAM). Sounds great. So I
switched, and everything w
18 matches
Mail list logo