The database as its stands it about 5GB, so a query on tracks was searching through just over 8 million records, on mysql this took about 7.5 seconds (without any performance playing) and postgres about 2 seconds.
Im running postgres with keys, indexing and the system also uses memcache so the calls are down to about 30ms The problem in trying to crush is for one page the sql looking through 4 tables. I could use ajax of course.. Thinking about it I kind of agree about the 'it should have that' statement, so ill include that and play about with that. On 22 Oct 2009, at 10:08, Will Jessop wrote: > > Replying to Matt as I don't have the original email. > > Just out of interest, how big are the tables, and how much space do > they take up? Can you show us an 'explain analyse' of a query that > would be optimised by this? > > I'd expect that lookups on the tables would all use indexes so like > Matt I am struggling to understand exactly how this will help. > > Will. > >> On Wed, Oct 21, 2009 at 2:51 PM, Alex Barlow <[email protected]> >> wrote: >> >> I have an ActiveRecord class called Releases and one called Albums, >> im >> merging to two tables together to a)save space and b)speed up sql >> called because theres no joins. > > -- > Will Jessop > Super Shiny Robot Limited - Professional web design and development > > t: 07939 547 962 > w: http://supershinyrobot.com/ > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
