Re: full text search

Can you run EXPLAIN on one of the queries and examine the query plan? If the query uses temporary tables and the result is too big then mysql will spill the temporary tables to disk and that can cause a significant slowdown.

Some good references on EXPLAIN:

• MySQL Explain – Reference
  
• EXPLAIN Demystified

-- Razvan ME

On Tue, Jul 17, 2012 at 10:39 PM, amber <tekipconsulting@gmail.com> wrote:

Hi all,

thanks to ur quick reply,

i m using nested queries to join to two table and  in googel cloud sql, we stored 100k of records and now while searching through google app its taking too much time and page not display anything.

and in log its showing following error,

This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application. 

On Tuesday, July 17, 2012 12:35:03 PM UTC+5:30, Razvan Musaloiu-E. wrote:

Do you mind providing a dataset and some examples of slow queries? Feel fre to contact me off list for this.

-- Razvan ME

On Mon, Jul 16, 2012 at 11:55 PM, amber <tekipconsulting@gmail.com> wrote:

Hi , 

I imported a DB (~100k rows) on which I am doing full text searches, 

In CloudSQL they are taking more than 30 seconds causing 

Apennine to exceed the request time limit. 

Any suggestions? Or are full text searches just too slow to be done in 

the GCS?