Re: Profiling and Performance

Which database are you using? Most databases has the ability to monitor performance, and single out queries and statements where most of the time is spent.

MySQL, for instance, has The Slow Query Log and the EXPLAIN command.

--
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]

Comment on Re: Profiling and Performance

Replies are listed 'Best First'.
Re^2: Profiling and Performance by Herkum (Parson) on Mar 27, 2009 at 16:09 UTC
I don't think that any individual query is slow so much as the number of queries. After sleeping on it last night, I figured out I was always using the DBI handle instead of storing a statement handle for a prepared statement. That being said I think I will try to cache the statement handle's and see if that offers any improvement.	[reply]
Re^3: Profiling and Performance by andreas1234567 (Vicar) on Mar 27, 2009 at 20:35 UTC
I don't think that any individual query is slow so much as the number of queries. Then shaving off a little time on each one can add up to a lot. Are you using placeholders? Have you considered stored procedures, possibly combining multiple operations into single? Are your data properly indexed? Are your tables unnecessarily large (can old data be deleted)? -- No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]	[reply]


XP is just a number
	PerlMonks