|
|
Posted by Jim Michaels on 10/04/21 11:37
one of the things you can do is reduce or avoid full table scans. these are
SELECTs that read through the entire table. if you can optimize your
queries to eliminate table scans (if they are complex ones it takes some
thinking), it will speed up your pages.
I had a web page that I used a lot of config variables in a table, and I hit
the database a lot. it slowed things down enough to be a bit noticeable.
I think it also depends on how much their servers are loaded down. I am
using fewer config variables on a different hosting service and things are
snappy.
<nc@iname.com> wrote in message
news:1135362495.577516.193040@z14g2000cwz.googlegroups.com...
> theseer@gmail.com wrote:
>>
>> What do most people out there think is a good maximum [approximate]
>> number of MySQL queries per pageload?
>
> I think you should reconsider your approach to the problem. Instead of
> wondering whether X queries per page is too much, you should take steps
> to reduce X as much as possible without loss of functionality and
> fine-tune your database server to your projected load level.
>
> Cheers,
> NC
>
Navigation:
[Reply to this message]
|