On Mon, 26 Jan 2009 14:51:29 lenz wrote: > you die with the updates/inserts in the DB as they lock the selects. to > speed things up here consider the usage of indexes on all columns that you > use after the where ... guess thats a start. consider using some other > mechanism might be an idea as well. depending on your complexity of the > data, mysql might not be the first choice, a simple key/value database > might do the trick at a higher performance, try postgresql and compare it > for this use case to mysql. just looking into one direction might not > always do the trick when things start to grow :-) > cheers > lenz
Thanks :-) It is already indexed. I am sure that there is room for improvement (and I have an idea) but at present I am working on the most important part which is removing the need for the ORDER BY rand() as this will be the biggest CPU sucker. --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to nzphpug@googlegroups.com To unsubscribe, send email to nzphpug+unsubscr...@googlegroups.com -~----------~----~----~----~------~----~------~--~---
