Hi Foo,
MyISAM impress me on insert speed, however on many case MyISAM is not
better than Innodb. If you can't use combination of them,
better your break down your need to decide which one to use. AFAIK, sub
query is better in innodb rather than myisam, and if you have only
200.000 records
Just want to share and confirm my findings on a performance issue I've been
experiencing.
My database is strictly non-transactional, but it's got about 200,000 records
in this particular table. The table has a primary index, and 2 integers - one
for the date and the other for the time. Among
Hey there Ady, Philip,
Thanks for the suggestions for the phenomenon. I also notice something
along the course of optimisation:
1. Sorting records with huge fields (ie: blobs, text) is significantly
slower than if you extract the blobs/ text fields into a separate table.
The record size makes
Hi all,
Just want to share and confirm my findings on a performance issue I've
been experiencing.
My database is strictly non-transactional, but it's got about 200,000
records in this particular table. The table has a primary index, and 2
integers - one for the date and the other for the
As far as i know, using IN( SUBQUERY ) will give very poor performance,
especially if the record set returned by the large query is really large.
try to use a join instead of WHERE IN( XXX )..
Im not sure why its that much better in INNODB though...
Foo Ji-Haw wrote:
Hi all,
Just want to
