TwelvestoneBack End

MySQL Indexes


Sign in

  • Waiting for Godot ( 730 k posts )
    Just conversation.
  • Thunder Dome ( 23 k posts )
    Photoshop Tennis and Collabs.
  • Photography ( 5.1 k posts )
    For all you shutterbugs, sh...
  • Flash ( 18 k posts )
    ActionScripting to tweens, ...
  • Front End ( 5.9 k posts )
    general front end design an...
  • Back End ( 9.7 k posts )
    serverside scripting, progr...
  • Projects and Theory ( 12 k posts )
    This forum is for discussio...
  • FAQ ( 269 posts )
    All those nagging questions...
  • Design ( 17 k posts )
    graphics & all aspects of g...
  • Purgatory ( 3.6 k posts )
    12stone Jail, feel free to ...
DontBogartMe
 
2011-09-04

just a heads up ... a page that was taking 38 seconds to render now renders in 0.2 seconds purely because I added indexes on the foreign key fields. I had no idea they could have such a massive effect. Bonus!

Stinky
 
2011-09-04

Heh, yeah. That's the difference between O(N) and O(logN). Instead of scanning every row in a table every time the database has to look for something it scans a few. Multiply that savings by the number of times something has to be joined and you'll see a big difference. A lot of people don't start to notice until their tables grow.

DontBogartMe
 
2011-09-04

Originally posted by: Stinky A lot of people don't start to notice until their tables grow.

yeah, it was all groovy until the real data started getting entered k

poliguin
 
2011-09-04

It's also interesting to see how people optimize queries.

Sorry, you must be a member to post to a conversation. Either log in or sign up to get involved.
TwelvestoneBack End

MySQL Indexes