Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Joining/optimizing Nightmare

forums › forums › SQLyog › Using SQLyog › Joining/optimizing Nightmare

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • October 24, 2006 at 5:18 pm #22849
      peterlaursen
      Participant

      two chances …

      * upgrade the server (or your resources on it)

      * upgrade the connection

      This is a single query and it is not SQLyog that is slow. SQLyog is patiently waiting for data to arrive! But try to include a “LIMIT 1000” for instance and measure the time. Your JOIN syntax could be wrong resulting in an astronomic rows returned.

      Also Check Task Manager. How much CPU is used? What is the network transfer rate?

    • October 24, 2006 at 6:28 pm #22850
      Paula
      Member

      The two tables are on my harddrive (400G:cool:. I'm running MySQL on my machine only. My syntax is simple:

      SELECT BIRTH.*, NAME.*

      FROM BIRTH INNER JOIN NAME on (BIRTH.LAST3 = NAME.LAST3) and (BIRTH.FIRST3 and NAME.FIRST3);

      When I check the CPU usage, it's going back and forth from about 7 pct to 22 pct.

      peterlaursen wrote on Oct 24 2006, 12:18 PM:
      two chances …

      * upgrade the server (or your resources on it)

      * upgrade the connection

      This is a single query and it is not SQLyog that is slow. SQLyog is patiently waiting for data to arrive! But try to include a “LIMIT 1000” for instance and measure the time. Your JOIN syntax could be wrong resulting in an astronomic rows returned.

      Also Check Task Manager. How much CPU is used? What is the network transfer rate?

    • October 25, 2006 at 4:24 am #22851
      peterlaursen
      Participant

      Well – then it is not the CPU that is the 'bottleneck' her. And no connection issue either.

      Did you try changing the server configuration? You find different 'templates' for the configuration file in the Server installation folder.

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.