Re: Advice about optomizing MYSQL

ZeldorBlat wrote:
maxdamage wrote:
Well, I was wondering if it would be better to do a series of smaller
queries (about 5 - 10) and use less overhead on the PHP end or do one
big querry that would fill a huge array (maybe 50x10) and use a ton of
overhead.

One big query. Trips to the database are generally expensive and a 50
x 10 array isn't very big at all. If all else fails, try the two and
see which performs better.

Keep in mind the distance to the mysql server from the machine running the php script. The further away the more risk for lag.


//Aho
.

Relevant Pages

  • Re: [PHP] the most amazing php code i have ever seen so far
    ... Then it will lazy load them and handle the ... This allows me to define a ton of classes for events and there ... isn't any overhead other than one array. ...
    (php.general)
  • Re: Advice about optomizing MYSQL
    ... big querry that would fill a huge array and use a ton of ... overhead. ... x 10 array isn't very big at all. ... Keep in mind the distance to the mysql server from the machine running the php script. ...
    (alt.php)
  • Advice about optomizing MYSQL
    ... big querry that would fill a huge array and use a ton of ... overhead. ...
    (alt.php)
  • Re: Text Script
    ... > more overhead than reading from an array as it is an in-memory operation. ... For small files this adds much overhead. ... >> Rewinding a file might indeed be instantaneous as you say, ... design time efficiency may be in the eye of the beholder - ...
    (microsoft.public.windows.server.scripting)
  • Re: Ada.Containers.Vectors - querying multiple elements
    ... there would be a distributed overhead. ... compilers store it separately. ... In order to be able to represent an array as ... so I don't think it would make sense to allow 'First to be an invalid ...
    (comp.lang.ada)