in reply to Re: A profiling surprise ...
in thread A profiling surprise ...
More specifically, shift the IO burden away from the connection between your program and the database.
- Never ask for more data from the database than your code will actually use. Let the DB winnow it down and return just what is needed. That means using proper queries with WHERE clauses and, if applicable, LIMIT clauses.
- Don't return unsorted information then sort it, as databases are good at sorting quickly.
- Use placeholders instead of building new queries from scratch by concatenation, as that helps the DB's execution engine minimize its work (more importantly, using placeholders can make SQL injection attacks much less likely anyway).
- If you're going to search on a particular column a lot, index it. If you're not searching on it much but you're going to sort on it fairly often, index it anyway.
- Select a row by primary key if you know it and want just that row.
I'm sure there are other monks with even better advice, but these will help quite a bit.
UPDATE: fixed thinko s/WHEN/WHERE/ (thanks, kyle, for pointing that out in a msg).
|Replies are listed 'Best First'.|
Re^3: A profiling surprise ...
by Jenda (Abbot) on May 24, 2008 at 13:04 UTC
In Section Seekers of Perl Wisdom