Coding efficiency

neville

I am writing an appointment scheduler and I have three queries running one after the other. I can also do it with one join query but that will take more time to arrange and test.

I was wondering if it is a better idea to go in for the latter [join query] or the former.

How many queries can one have on one page at the most without making little or no compromise on efficiency ?

Anon

I cannot advice smth about your queries without seing them but just to be sure - are you using indexes? I had once a problem that my database worked slowly and I solved the problem with just optimizing indexes - complex indexes when needed with correct consequence of the fields :-)

simon_belak

if you are not using VERY complex joins, it is better to do it in one query. Why? Mainly becouse this way is usualy lighhter on memory (and if the db and web server are seperated bandwidth) and becouse you make less db api calls this way.
But this is just a general principle. For you it might be better the other way around.
And as Annchen pointed out check your indexes!

neville

Thanks Annchen and Simon .... I was just wondering how many queries and how many disk reads can I put for a medium to large program without making it a badly coded program. How do I check the performance of my code under various bandwidths and other such variables. There aren't many gifs on the page and total size of one page view including all file includes and gifs works out to 30 kb. There are 4 includes and 8 queries happening for the same.

Is this ok or should it be lesser ?