Re: Different performance between 1.1 and 1.2

[phpjoy]

Fear is the path to the dark side. Fear leads to anger. Anger leads
to hate. Hate leads to suffering.

Not that I'm hinting anything :D


On May 30, 12:13 am, Chris Hartjes [EMAIL PROTECTED] wrote:
 On Thu, May 29, 2008 at 4:56 PM, [EMAIL PROTECTED]

 [EMAIL PROTECTED] wrote:

  The problem is that it's the same even if debug is off .
  The difference is smaller but Cake 1.1 seems faster than Cake 1.2

 Ah, you crazy kids and your concerns about the speed of Cake.  Back in
 my day, we looked at all factors of an application before we started
 blaming the code, since the database would inevitably be the
 bottleneck unless we had written really shitty code or were actually
 doing computationally-intensive work.

 I think the additional features of 1.2 are what make it worth
 upgrading from 1.1, and I hate to burst anyone's ego but I doubt your
 application will get so much traffic that any alleged speed decrease
 from Cake 1.2 will make a difference.  Good coding practices go a long
 way towards ensuring application speed.

 Performance testing and benchmarking is an art in itself and unless
 you use tools specifically dedicated towards those  ends (like Xdebug
 or Apache Benchmark or Siege ) you are just making shit up.

 Have I used these tools on Cake?  No.  Why? Because I don't care about
 CakePHP's speed.  For 99.999% of those who use CakePHP, it is
 MTFEIYFTR (More Than Fast Enough If You Follow The Rules).  For the
 other .001%, either change your code or go with a non-Cake solution.

 This is the Twitter sucks because of Rails fallacy.  Twitter sucks
 because they built a messaging system using tools for building a
 content management system.

 So, to get back to your initial question from the beginning of the thread:

 Upgrade to 1.2 because it is light-years ahead of 1.1 in available features.

 Now get off my lawn!

 --
 Chris Hartjes
 Internet Loudmouth
 Motto for 2008: Moving from herding elephants to handling snakes...
 @TheKeyBoard:http://www.littlehart.net/atthekeyboard
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

Only one thing : A gentleman.
I a person use a forum It's for learn and not to say that your
framework is a crap.
If I use Cakephp maybe it's because I think that is light-years ahead
of other frameworks.
I post my code so you can see if I use good coding practices.



class User extends AppModel
{
var $useDbConfig = myDb;
var $name = 'User';
var $useTable =user;


var $primaryKey =username;


var $hasAndBelongsToMany = array('Network' =

array('className'= 'Network',
  'joinTable'= 'utente_gruppo',
  'foreignKey'   = 'username',
  'associationForeignKey'= 'gruppo_id',

'order'= 'gruppo_nome ASC'
));


var $hasMany = array('Ente' =array('className'= 'Ente',
 'foreignKey'   = '',

'finderQuery'  = 'SELECT '
),
 'Team' =array('className'=
'Team',
   'foreignKey'   = '',

'finderQuery'  = 'SELECT ...'
 )
);





}




class UserController extends AppController
{
var $name = 'User';

   var $uses=array('Ente','Network','User','Team');

   var $components = array('Auth');

   function index($username=)
{
  $utente = $this-User-read('',$username);

 echo pre;
 pr($utente);
 echo /pre;

 $this-set('utente',$utente);
}

}

 The view is empty.




On 29 Mag, 23:13, Chris Hartjes [EMAIL PROTECTED] wrote:
 On Thu, May 29, 2008 at 4:56 PM, [EMAIL PROTECTED]

 [EMAIL PROTECTED] wrote:

  The problem is that it's the same even if debug is off .
  The difference is smaller but Cake 1.1 seems faster than Cake 1.2

 Ah, you crazy kids and your concerns about the speed of Cake.  Back in
 my day, we looked at all factors of an application before we started
 blaming the code, since the database would inevitably be the
 bottleneck unless we had written really shitty code or were actually
 doing computationally-intensive work.

 I think the additional features of 1.2 are what make it worth
 upgrading from 1.1, and I hate to burst anyone's ego but I doubt your
 application will get so much traffic that any alleged speed decrease
 from Cake 1.2 will make a difference.  Good coding practices go a long
 way towards ensuring application speed.

 Performance testing and benchmarking is an art in itself and unless
 you use tools specifically dedicated towards those  ends (like Xdebug
 or Apache Benchmark or Siege ) you are just making shit up.

 Have I used these tools on Cake?  No.  Why? Because I don't care about
 CakePHP's speed.  For 99.999% of those who use CakePHP, it is
 MTFEIYFTR (More Than Fast Enough If You Follow The Rules).  For the
 other .001%, either change your code or go with a non-Cake solution.

 This is the Twitter sucks because of Rails fallacy.  Twitter sucks
 because they built a messaging system using tools for building a
 content management system.

 So, to get back to your initial question from the beginning of the thread:

 Upgrade to 1.2 because it is light-years ahead of 1.1 in available features.

 Now get off my lawn!

 --
 Chris Hartjes
 Internet Loudmouth
 Motto for 2008: Moving from herding elephants to handling snakes...
 @TheKeyBoard:http://www.littlehart.net/atthekeyboard
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

Sorry there is an error I use print_r instead of pr because the debug
is set on 0

On 30 Mag, 09:28, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 Only one thing : A gentleman.
 I a person use a forum It's for learn and not to say that your
 framework is a crap.
 If I use Cakephp maybe it's because I think that is light-years ahead
 of other frameworks.
 I post my code so you can see if I use good coding practices.

 class User extends AppModel
 {
     var $useDbConfig = myDb;
     var $name = 'User';
     var $useTable =user;

     var $primaryKey =username;

     var $hasAndBelongsToMany = array('Network' =

 array('className'    = 'Network',
                                           'joinTable'    = 'utente_gruppo',
                                   'foreignKey'   = 'username',
                                   'associationForeignKey'= 'gruppo_id',

 'order'        = 'gruppo_nome ASC'
                                 ));

     var $hasMany = array('Ente' =array('className'    = 'Ente',
                                  'foreignKey'   = '',

 'finderQuery'  = 'SELECT '
                             ),
                                      'Team' =array('className'    =
 'Team',
                                    'foreignKey'   = '',

 'finderQuery'  = 'SELECT ...'
                              )
                     );

 }

 class UserController extends AppController
 {
     var $name = 'User';

    var $uses=array('Ente','Network','User','Team');

    var $components = array('Auth');

    function index($username=)
     {
       $utente = $this-User-read('',$username);

      echo pre;
      pr($utente);
      echo /pre;

      $this-set('utente',$utente);
     }

 }

  The view is empty.

 On 29 Mag, 23:13, Chris Hartjes [EMAIL PROTECTED] wrote:



  On Thu, May 29, 2008 at 4:56 PM, [EMAIL PROTECTED]

  [EMAIL PROTECTED] wrote:

   The problem is that it's the same even if debug is off .
   The difference is smaller but Cake 1.1 seems faster than Cake 1.2

  Ah, you crazy kids and your concerns about the speed of Cake.  Back in
  my day, we looked at all factors of an application before we started
  blaming the code, since the database would inevitably be the
  bottleneck unless we had written really shitty code or were actually
  doing computationally-intensive work.

  I think the additional features of 1.2 are what make it worth
  upgrading from 1.1, and I hate to burst anyone's ego but I doubt your
  application will get so much traffic that any alleged speed decrease
  from Cake 1.2 will make a difference.  Good coding practices go a long
  way towards ensuring application speed.

  Performance testing and benchmarking is an art in itself and unless
  you use tools specifically dedicated towards those  ends (like Xdebug
  or Apache Benchmark or Siege ) you are just making shit up.

  Have I used these tools on Cake?  No.  Why? Because I don't care about
  CakePHP's speed.  For 99.999% of those who use CakePHP, it is
  MTFEIYFTR (More Than Fast Enough If You Follow The Rules).  For the
  other .001%, either change your code or go with a non-Cake solution.

  This is the Twitter sucks because of Rails fallacy.  Twitter sucks
  because they built a messaging system using tools for building a
  content management system.

  So, to get back to your initial question from the beginning of the thread:

  Upgrade to 1.2 because it is light-years ahead of 1.1 in available features.

  Now get off my lawn!

  --
  Chris Hartjes
  Internet Loudmouth
  Motto for 2008: Moving from herding elephants to handling snakes...
  @TheKeyBoard:http://www.littlehart.net/atthekeyboard- Nascondi testo tra 
  virgolette -

 - Mostra testo tra virgolette -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[Marcin Domanski]

hey

 Ah, you crazy kids and your concerns about the speed of Cake.  Back in
 my day, we looked at all factors of an application before we started
 blaming the code, since the database would inevitably be the
 bottleneck unless we had written really shitty code or were actually
 doing computationally-intensive work.

 I think the additional features of 1.2 are what make it worth
 upgrading from 1.1, and I hate to burst anyone's ego but I doubt your
 application will get so much traffic that any alleged speed decrease
 from Cake 1.2 will make a difference.  Good coding practices go a long
 way towards ensuring application speed.

 Performance testing and benchmarking is an art in itself and unless
 you use tools specifically dedicated towards those  ends (like Xdebug
 or Apache Benchmark or Siege ) you are just making shit up.

 Have I used these tools on Cake?  No.  Why? Because I don't care about
 CakePHP's speed.  For 99.999% of those who use CakePHP, it is
 MTFEIYFTR (More Than Fast Enough If You Follow The Rules).  For the
 other .001%, either change your code or go with a non-Cake solution.

 This is the Twitter sucks because of Rails fallacy.  Twitter sucks
 because they built a messaging system using tools for building a
 content management system.

 So, to get back to your initial question from the beginning of the thread:

 Upgrade to 1.2 because it is light-years ahead of 1.1 in available features.

 Now get off my lawn!
Give him a beer!

Just to elaborate on twitter problems if anyone is interested in some
good reads:
http://www.hueniverse.com/hueniverse/2008/03/on-scaling-a-mi.html
http://www.hueniverse.com/hueniverse/2008/03/scaling-a-micro.html



-- 
Marcin Domanski
http://kabturek.info

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[Marcin Domanski]

Hey,

 Only one thing : A gentleman.
 I a person use a forum It's for learn and not to say that your
 framework is a crap.
Who said something about crap ?
 If I use Cakephp maybe it's because I think that is light-years ahead
 of other frameworks.
You're right here ;)
 I post my code so you can see if I use good coding practices.



 class User extends AppModel
 {
var $useDbConfig = myDb;
var $name = 'User';
var $useTable =user;


var $primaryKey =username;


var $hasAndBelongsToMany = array('Network' =

 array('className'= 'Network',
  'joinTable'= 'utente_gruppo',
  'foreignKey'   = 'username',
  'associationForeignKey'= 'gruppo_id',

 'order'= 'gruppo_nome ASC'
));


var $hasMany = array('Ente' =array('className'= 'Ente',
 'foreignKey'   = '',

 'finderQuery'  = 'SELECT '
),
 'Team' =array('className'=
 'Team',
   'foreignKey'   = '',

 'finderQuery'  = 'SELECT ...'
 )
);
apart from that you don't use bind/unbind/contain whatever, you don't
set the needed field in the associations (really need all ?)





 }




 class UserController extends AppController
 {
var $name = 'User';

   var $uses=array('Ente','Network','User','Team');
this is certainly_not_ good coding practice especially if they are associated.
you only need User there - and since its default then you can drop the
whole line.
$this-Model-AssociatedModel-find()

   var $components = array('Auth');

   function index($username=)
{
  $utente = $this-User-read('',$username);
aren't you find-ing a user with a username ? or read.ing the username
with the it ? (there is a difference- api)

 echo pre;
 pr($utente);
 echo /pre;

 $this-set('utente',$utente);
}

 }

  The view is empty.
if you don't have a view = $this-autoRender = false;


And people code in English for a reason - so other people can
understand the code ;)

HTH,

-- 
Marcin Domanski
http://kabturek.info

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

On 28 Mag, 19:33, Joel Perras [EMAIL PROTECTED] wrote:
 On May 28, 12:58 pm, [EMAIL PROTECTED]

 [EMAIL PROTECTED] wrote:
  With debug=2 the queries are exaclty equal except for the DESCRIBE
  operation on the joinTable.

 As I stated previously, when debug = 0 these queries are cached.

  Perhaps it'is a my feeling.
  Exist a instrument for evalute the time loading of a scripts?

 A quick and dirty way of benchmarking page rendering time would be to
 put a call to microtime() in app_controller.php in both the
 beforeRender() and afterFilter() methods, and echo/log the time
 difference between the two.

I use this method and I test this case

In cake 1.2 : a controller -action with one read operation ;
controller uses one model.
  debug: 2

In cake 1.1 : a controller -action with one read operation ;
controller uses teen model.
   debug: 2

Using microtime in app_controller.php  I get that:

Cake1.2 is always over 100ms

Cake 1.1 is always over 60ms

The incredible thing is that from debug it seems that the controller-
action in Cake 1.1 makes more queries (DESCRIBE query) because it has
to load more models that cake 1.2





  Is it possible to use eAccelarator with Cake 1.2?

 Cake actually uses Memcache (a PHP wrapper for memcached) for
 caching.  Sadly there isn't anything in book.cakephp.org describing
 this (yet), but a few well placed google queries and a quick search of
 this group should give you an idea of how things work.  I've never
 used eAccelerator, but I've heard of other people who have used it in
 conjunction with Cake.

 -Joel.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[djiize]

Don't do benchmark with debug on, it's useless.
Even if Cake 1.1 is faster than 1.2 with debug on, it won't tell you
if it's the same when debug is off !

On 29 mai, 17:31, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 On 28 Mag, 19:33, Joel Perras [EMAIL PROTECTED] wrote:

  On May 28, 12:58 pm, [EMAIL PROTECTED]

  [EMAIL PROTECTED] wrote:
   With debug=2 the queries are exaclty equal except for the DESCRIBE
   operation on the joinTable.

  As I stated previously, when debug = 0 these queries are cached.

   Perhaps it'is a my feeling.
   Exist a instrument for evalute the time loading of a scripts?

  A quick and dirty way of benchmarking page rendering time would be to
  put a call to microtime() in app_controller.php in both the
  beforeRender() and afterFilter() methods, and echo/log the time
  difference between the two.

 I use this method and I test this case

 In cake 1.2 : a controller -action with one read operation ;
 controller uses one model.
                   debug: 2

 In cake 1.1 : a controller -action with one read operation ;
 controller uses teen model.
                    debug: 2

 Using microtime in app_controller.php  I get that:

 Cake1.2 is always over 100ms

 Cake 1.1 is always over 60ms

 The incredible thing is that from debug it seems that the controller-
 action in Cake 1.1 makes more queries (DESCRIBE query) because it has
 to load more models that cake 1.2

   Is it possible to use eAccelarator with Cake 1.2?

  Cake actually uses Memcache (a PHP wrapper for memcached) for
  caching.  Sadly there isn't anything in book.cakephp.org describing
  this (yet), but a few well placed google queries and a quick search of
  this group should give you an idea of how things work.  I've never
  used eAccelerator, but I've heard of other people who have used it in
  conjunction with Cake.

  -Joel.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[mark_story]

On May 28, 12:58 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 With debug=2 the queries are exaclty equal except for the DESCRIBE
 operation on the joinTable.
 Perhaps it'is a my feeling.
 Exist a instrument for evalute the time loading of a scripts?
 Is it possible to use eAccelarator with Cake 1.2?


Another way to track the execution time is to use Xdebug's profiling
facilities. After installing and turning on xdebug, and its
profiling.  You can request a page with XDEBUG_PROFILE as a get
parameter, and xdebug will create a cachegrind that you can analyze in
KCacheGrind or WinCacheGrind.  That will give you function call times,
how many and how long each function takes.

-Mark

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

On 29 Mag, 18:12, djiize [EMAIL PROTECTED] wrote:
 Don't do benchmark with debug on, it's useless.
 Even if Cake 1.1 is faster than 1.2 with debug on, it won't tell you
 if it's the same when debug is off !


The problem is that it's the same even if debug is off .
The difference is smaller but Cake 1.1 seems faster than Cake 1.2


 On 29 mai, 17:31, [EMAIL PROTECTED]

 [EMAIL PROTECTED] wrote:
  On 28 Mag, 19:33, Joel Perras [EMAIL PROTECTED] wrote:

   On May 28, 12:58 pm, [EMAIL PROTECTED]

   [EMAIL PROTECTED] wrote:
With debug=2 the queries are exaclty equal except for the DESCRIBE
operation on the joinTable.

   As I stated previously, when debug = 0 these queries are cached.

Perhaps it'is a my feeling.
Exist a instrument for evalute the time loading of a scripts?

   A quick and dirty way of benchmarking page rendering time would be to
   put a call to microtime() in app_controller.php in both the
   beforeRender() and afterFilter() methods, and echo/log the time
   difference between the two.

  I use this method and I test this case

  In cake 1.2 : a controller -action with one read operation ;
  controller uses one model.
debug: 2

  In cake 1.1 : a controller -action with one read operation ;
  controller uses teen model.
 debug: 2

  Using microtime in app_controller.php  I get that:

  Cake1.2 is always over 100ms

  Cake 1.1 is always over 60ms

  The incredible thing is that from debug it seems that the controller-
  action in Cake 1.1 makes more queries (DESCRIBE query) because it has
  to load more models that cake 1.2

Is it possible to use eAccelarator with Cake 1.2?

   Cake actually uses Memcache (a PHP wrapper for memcached) for
   caching.  Sadly there isn't anything in book.cakephp.org describing
   this (yet), but a few well placed google queries and a quick search of
   this group should give you an idea of how things work.  I've never
   used eAccelerator, but I've heard of other people who have used it in
   conjunction with Cake.

   -Joel.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[Chris Hartjes]

On Thu, May 29, 2008 at 4:56 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:


 The problem is that it's the same even if debug is off .
 The difference is smaller but Cake 1.1 seems faster than Cake 1.2


Ah, you crazy kids and your concerns about the speed of Cake.  Back in
my day, we looked at all factors of an application before we started
blaming the code, since the database would inevitably be the
bottleneck unless we had written really shitty code or were actually
doing computationally-intensive work.

I think the additional features of 1.2 are what make it worth
upgrading from 1.1, and I hate to burst anyone's ego but I doubt your
application will get so much traffic that any alleged speed decrease
from Cake 1.2 will make a difference.  Good coding practices go a long
way towards ensuring application speed.

Performance testing and benchmarking is an art in itself and unless
you use tools specifically dedicated towards those  ends (like Xdebug
or Apache Benchmark or Siege ) you are just making shit up.

Have I used these tools on Cake?  No.  Why? Because I don't care about
CakePHP's speed.  For 99.999% of those who use CakePHP, it is
MTFEIYFTR (More Than Fast Enough If You Follow The Rules).  For the
other .001%, either change your code or go with a non-Cake solution.

This is the Twitter sucks because of Rails fallacy.  Twitter sucks
because they built a messaging system using tools for building a
content management system.

So, to get back to your initial question from the beginning of the thread:

Upgrade to 1.2 because it is light-years ahead of 1.1 in available features.

Now get off my lawn!

-- 
Chris Hartjes
Internet Loudmouth
Motto for 2008: Moving from herding elephants to handling snakes...
@TheKeyBoard: http://www.littlehart.net/atthekeyboard

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

Hi
I have a question.
I upgrade my applications from 1.1.13 to 1.2
I have noted that the same application in 1.2 is slower than the same
application on 1.1.13.
I use $this-Model-unbind and $this-Model-recursive=-1   in my
applications.
I have two query:
1) In Cake 1.2 for use $this-Model-unbind and $this-Model-
recursive=-1 I have to set some $actas or they work even if I have no
$actas setted?
2)I have analized queries (debug set 2) and I see that there are some
queries to determinate fields of the join tables of the HABTM's
relation (DESCRIBE  ) .Is it possible to do that my application
doesn't execute these queries?

Many Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[Joel Perras]

When you set your debug configure level above 0 (which you have done
to be able to see the relevant SQL queires), the model caches are
refreshed.  When in production mode (debug level of 0), the DESCRIBE
query results are cached.

You'll have to be more specific when saying 'is slower than the same
application on 1.1.13' to get any useful information on how to
optimize.  Is there more data being sent to the views than necessary?
Are there superfluous queries being run?  Have you changed anything
else since your upgrade, i.e. controller logic, model logic, etc.?

-Joel.

On May 28, 9:49 am, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 Hi
 I have a question.
 I upgrade my applications from 1.1.13 to 1.2
 I have noted that the same application in 1.2 is slower than the same
 application on 1.1.13.
 I use $this-Model-unbind and $this-Model-recursive=-1   in my
 applications.
 I have two query:
 1) In Cake 1.2 for use $this-Model-unbind and $this-Model-recursive=-1 I 
 have to set some $actas or they work even if I have no

 $actas setted?
 2)I have analized queries (debug set 2) and I see that there are some
 queries to determinate fields of the join tables of the HABTM's
 relation (DESCRIBE  ) .Is it possible to do that my application
 doesn't execute these queries?

 Many Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

I have change a bit of code but only not important (for example
loadModule with App::import('Model', .);  , I have inserted the
RequestHandler )
I don't have instruments for mesaurement the execution of script.
But I can see clearly the the loading of the same page  (a very simple
page) is slower in cake 1.2.


On 28 Mag, 17:29, Joel Perras [EMAIL PROTECTED] wrote:
 When you set your debug configure level above 0 (which you have done
 to be able to see the relevant SQL queires), the model caches are
 refreshed.  When in production mode (debug level of 0), the DESCRIBE
 query results are cached.

 You'll have to be more specific when saying 'is slower than the same
 application on 1.1.13' to get any useful information on how to
 optimize.  Is there more data being sent to the views than necessary?
 Are there superfluous queries being run?  Have you changed anything
 else since your upgrade, i.e. controller logic, model logic, etc.?

 -Joel.

 On May 28, 9:49 am, [EMAIL PROTECTED]



 [EMAIL PROTECTED] wrote:
  Hi
  I have a question.
  I upgrade my applications from 1.1.13 to 1.2
  I have noted that the same application in 1.2 is slower than the same
  application on 1.1.13.
  I use $this-Model-unbind and $this-Model-recursive=-1   in my
  applications.
  I have two query:
  1) In Cake 1.2 for use $this-Model-unbind and $this-Model-recursive=-1 
  I have to set some $actas or they work even if I have no

  $actas setted?
  2)I have analized queries (debug set 2) and I see that there are some
  queries to determinate fields of the join tables of the HABTM's
  relation (DESCRIBE  ) .Is it possible to do that my application
  doesn't execute these queries?

  Many Thanks- Nascondi testo tra virgolette -

 - Mostra testo tra virgolette -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[[EMAIL PROTECTED]]

With debug=2 the queries are exaclty equal except for the DESCRIBE
operation on the joinTable.
Perhaps it'is a my feeling.
Exist a instrument for evalute the time loading of a scripts?
Is it possible to use eAccelarator with Cake 1.2?


On 28 Mag, 18:43, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 I have change a bit of code but only not important (for example
 loadModule with App::import('Model', .);  , I have inserted the
 RequestHandler )
 I don't have instruments for mesaurement the execution of script.
 But I can see clearly the the loading of the same page  (a very simple
 page) is slower in cake 1.2.

 On 28 Mag, 17:29, Joel Perras [EMAIL PROTECTED] wrote:



  When you set your debug configure level above 0 (which you have done
  to be able to see the relevant SQL queires), the model caches are
  refreshed.  When in production mode (debug level of 0), the DESCRIBE
  query results are cached.

  You'll have to be more specific when saying 'is slower than the same
  application on 1.1.13' to get any useful information on how to
  optimize.  Is there more data being sent to the views than necessary?
  Are there superfluous queries being run?  Have you changed anything
  else since your upgrade, i.e. controller logic, model logic, etc.?

  -Joel.

  On May 28, 9:49 am, [EMAIL PROTECTED]

  [EMAIL PROTECTED] wrote:
   Hi
   I have a question.
   I upgrade my applications from 1.1.13 to 1.2
   I have noted that the same application in 1.2 is slower than the same
   application on 1.1.13.
   I use $this-Model-unbind and $this-Model-recursive=-1   in my
   applications.
   I have two query:
   1) In Cake 1.2 for use $this-Model-unbind and 
   $this-Model-recursive=-1 I have to set some $actas or they work even if 
   I have no

   $actas setted?
   2)I have analized queries (debug set 2) and I see that there are some
   queries to determinate fields of the join tables of the HABTM's
   relation (DESCRIBE  ) .Is it possible to do that my application
   doesn't execute these queries?

   Many Thanks- Nascondi testo tra virgolette -

  - Mostra testo tra virgolette -- Nascondi testo tra virgolette -

 - Mostra testo tra virgolette -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---

Re: Different performance between 1.1 and 1.2

[Joel Perras]

On May 28, 12:58 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 With debug=2 the queries are exaclty equal except for the DESCRIBE
 operation on the joinTable.

As I stated previously, when debug = 0 these queries are cached.
 Perhaps it'is a my feeling.
 Exist a instrument for evalute the time loading of a scripts?

A quick and dirty way of benchmarking page rendering time would be to
put a call to microtime() in app_controller.php in both the
beforeRender() and afterFilter() methods, and echo/log the time
difference between the two.

 Is it possible to use eAccelarator with Cake 1.2?

Cake actually uses Memcache (a PHP wrapper for memcached) for
caching.  Sadly there isn't anything in book.cakephp.org describing
this (yet), but a few well placed google queries and a quick search of
this group should give you an idea of how things work.  I've never
used eAccelerator, but I've heard of other people who have used it in
conjunction with Cake.


-Joel.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---