Re: [CakePHP : The Rapid Development Framework for PHP] #4367: File Searching Kills Performance

[CakePHP : The Rapid Development Framework for PHP]

#4367: File Searching Kills Performance
-+--
Reporter:  andyic3   | Owner:  
Type:  Optimization  |Status:  reopened
Priority:  Critical  | Milestone:  1.3.x.x 
   Component:  File System   |   Version:  
Severity:  Critical  |Resolution:  
Keywords:|   Php_version:  n/a 
Cake_version:|  
-+--
Comment (by AbhimanyuG):

 Same problem: https://trac.cakephp.org/ticket/6143

 #6143 can be closed.

-- 
Ticket URL: 
CakePHP : The Rapid Development Framework for PHP 
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to 
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~--~~~~--~~--~--~---

Re: [CakePHP : The Rapid Development Framework for PHP] #4367: File Searching Kills Performance

[CakePHP : The Rapid Development Framework for PHP]

#4367: File Searching Kills Performance
-+--
Reporter:  andyic3   | Owner:  
Type:  Optimization  |Status:  reopened
Priority:  Critical  | Milestone:  1.2.x.x 
   Component:  File System   |   Version:  RC1 
Severity:  Critical  |Resolution:  
Keywords:|   Php_version:  n/a 
Cake_version:|  
-+--
Changes (by gwoo):

  * type:  Bug => Optimization

-- 
Ticket URL: 
CakePHP : The Rapid Development Framework for PHP 
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~--~~~~--~~--~--~---

Re: [CakePHP : The Rapid Development Framework for PHP] #4367: File Searching Kills Performance

[CakePHP : The Rapid Development Framework for PHP]

#4367: File Searching Kills Performance
+---
Reporter:  andyic3  | Owner:  
Type:  Bug  |Status:  reopened
Priority:  Critical | Milestone:  1.2.x.x 
   Component:  File System  |   Version:  RC1 
Severity:  Critical |Resolution:  
Keywords:   |   Php_version:  n/a 
Cake_version:   |  
+---
Changes (by reefnet_alex):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 Wait on guys, it looks to me like there could be an easy performance win
 here which is being dismissed.

 I will give another example of where we're seeing crippling performance
 through using App::import and mayb this will shed some more light on this
 as a genuine issue.

 We were using
 App::import('Vendor', 'mylib/myfile');

 to load some library files. Xdebug and valgrind were showing that the app
 was spending an age here. Stepping through you see that App::import does
 the following:

 1) it knows where the two vendors folders are - core and app
 2) as it doesn't currently have the app vendors paths stored in app it
 does a Folder->tree on the vendors paths loading in *each and every one*
 of the folders in vendors.
 3) it then checks to see if it found folder mylib and if it did checks to
 see if it contains the file you are looking for.

 It's this step 2 which is very slow. We (like a lot of people I suspect)
 use Zend framework as a good set of libraries for various useful bits and
 pieces. Zend is huge and sprawling though only loads what it needs so it
 generally an easy win to add in and cherry pick from. However, if you put
 it in your vendors folder (which to my mind seems a very logical place to
 keep it) the system takes a battering the first
 App::import('Vendor','blah') you do as it chunks it's way through the
 entire Zend tree just in case the thing you are looking in is in there.

 It would seem to me to be an easy win to get the Find to look for the
 folder:
 app/vendors/mylib

 rather than chunking its way through the entire vendors tree.

 It's easy enough to work around IF people are warned about it. You'd
 rarely need App::import's ability to help you override one class with
 another with vendors, so it's really being used as an expensive 'require'.
 In this case, just use a require. I'd think most people, getting used to
 the "Cake" way would App::import though. Generally it will work fine, but
 the day you decide to add that big library your app will die on it's knees
 and you'll have no idea why.

-- 
Ticket URL: 
CakePHP : The Rapid Development Framework for PHP 
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~--~~~~--~~--~--~---