what can I do to speed up bootstrap beforeFilter ?
Hi, I have been migrating an application to 1.2 and partly because of some threads about performance and benchmarking I have done my own comparisons. Loading up a simple login form for my app (just Auth no ACL) 1.1 is 8-10 times faster. 1.2 quickly catches up on more complete requests with a running session and more data. I was wondering of there was something I could do to my application to speed up Cake's initial overhead? I thought it might be some of my code but the time seem to be lost between bootstrap.php and the beforeFilter. Dropping all components does very little so I am guessing that if any time can be saved it has to be in routing or by some opcode caching. My server has eAccelerator running. Is there any experience of problems using eAccelerator (or APC) with 1.2 or anything like that which could explain the difference? Or , maybe I should say is there anything I may have forgotten to do that would make opcode caching work more efficiently on 1.2? I want to be clear about a few things. 1. I am talking about pretty small numbers here. Hundreds of seconds, not minutes. The total overhead on my server is about 0.06-0.08 sec depending on the mood of the server. 1.1 is usually another 0 down at about 0.008 sec. 1.2 is fast but 1.1 is damn fast, which is slightly annoying :) 2. This is not a big problem for this application on this server but I do have another project where the hardware is being pushed a lot more. This is me learning more about optimization. I am not looking to trim away anything in the core to gain speed but if there is something I can do to help the core boot faster I'd like give it a try. As always, any insights shared are greatly appreciated. /Martin --~--~-~--~~~---~--~~ 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: what can I do to speed up bootstrap beforeFilter ?
You have debug at 0, I presume? On Nov 6, 2:35 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have been migrating an application to 1.2 and partly because of some threads about performance and benchmarking I have done my own comparisons. Loading up a simple login form for my app (just Auth no ACL) 1.1 is 8-10 times faster. 1.2 quickly catches up on more complete requests with a running session and more data. I was wondering of there was something I could do to my application to speed up Cake's initial overhead? I thought it might be some of my code but the time seem to be lost between bootstrap.php and the beforeFilter. Dropping all components does very little so I am guessing that if any time can be saved it has to be in routing or by some opcode caching. My server has eAccelerator running. Is there any experience of problems using eAccelerator (or APC) with 1.2 or anything like that which could explain the difference? Or , maybe I should say is there anything I may have forgotten to do that would make opcode caching work more efficiently on 1.2? I want to be clear about a few things. 1. I am talking about pretty small numbers here. Hundreds of seconds, not minutes. The total overhead on my server is about 0.06-0.08 sec depending on the mood of the server. 1.1 is usually another 0 down at about 0.008 sec. 1.2 is fast but 1.1 is damn fast, which is slightly annoying :) 2. This is not a big problem for this application on this server but I do have another project where the hardware is being pushed a lot more. This is me learning more about optimization. I am not looking to trim away anything in the core to gain speed but if there is something I can do to help the core boot faster I'd like give it a try. As always, any insights shared are greatly appreciated. /Martin --~--~-~--~~~---~--~~ 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: what can I do to speed up bootstrap beforeFilter ?
It does not make much difference to the time either way actually. debug 0 results are more often down around 0.06 and debug 1 is more often around 0.08 or maybe up to 0.1 at times. On Nov 6, 8:42 pm, teknoid [EMAIL PROTECTED] wrote: You have debug at 0, I presume? On Nov 6, 2:35 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have been migrating an application to 1.2 and partly because of some threads about performance and benchmarking I have done my own comparisons. Loading up a simple login form for my app (just Auth no ACL) 1.1 is 8-10 times faster. 1.2 quickly catches up on more complete requests with a running session and more data. I was wondering of there was something I could do to my application to speed up Cake's initial overhead? I thought it might be some of my code but the time seem to be lost between bootstrap.php and the beforeFilter. Dropping all components does very little so I am guessing that if any time can be saved it has to be in routing or by some opcode caching. My server has eAccelerator running. Is there any experience of problems using eAccelerator (or APC) with 1.2 or anything like that which could explain the difference? Or , maybe I should say is there anything I may have forgotten to do that would make opcode caching work more efficiently on 1.2? I want to be clear about a few things. 1. I am talking about pretty small numbers here. Hundreds of seconds, not minutes. The total overhead on my server is about 0.06-0.08 sec depending on the mood of the server. 1.1 is usually another 0 down at about 0.008 sec. 1.2 is fast but 1.1 is damn fast, which is slightly annoying :) 2. This is not a big problem for this application on this server but I do have another project where the hardware is being pushed a lot more. This is me learning more about optimization. I am not looking to trim away anything in the core to gain speed but if there is something I can do to help the core boot faster I'd like give it a try. As always, any insights shared are greatly appreciated. /Martin --~--~-~--~~~---~--~~ 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: what can I do to speed up bootstrap beforeFilter ?
Well, that really depends on the way the app is setup. With debug 0 you are completely bypassing the Debugger, so it should definitely improve some things. On Nov 6, 3:00 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: It does not make much difference to the time either way actually. debug 0 results are more often down around 0.06 and debug 1 is more often around 0.08 or maybe up to 0.1 at times. On Nov 6, 8:42 pm, teknoid [EMAIL PROTECTED] wrote: You have debug at 0, I presume? On Nov 6, 2:35 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have been migrating an application to 1.2 and partly because of some threads about performance and benchmarking I have done my own comparisons. Loading up a simple login form for my app (just Auth no ACL) 1.1 is 8-10 times faster. 1.2 quickly catches up on more complete requests with a running session and more data. I was wondering of there was something I could do to my application to speed up Cake's initial overhead? I thought it might be some of my code but the time seem to be lost between bootstrap.php and the beforeFilter. Dropping all components does very little so I am guessing that if any time can be saved it has to be in routing or by some opcode caching. My server has eAccelerator running. Is there any experience of problems using eAccelerator (or APC) with 1.2 or anything like that which could explain the difference? Or , maybe I should say is there anything I may have forgotten to do that would make opcode caching work more efficiently on 1.2? I want to be clear about a few things. 1. I am talking about pretty small numbers here. Hundreds of seconds, not minutes. The total overhead on my server is about 0.06-0.08 sec depending on the mood of the server. 1.1 is usually another 0 down at about 0.008 sec. 1.2 is fast but 1.1 is damn fast, which is slightly annoying :) 2. This is not a big problem for this application on this server but I do have another project where the hardware is being pushed a lot more. This is me learning more about optimization. I am not looking to trim away anything in the core to gain speed but if there is something I can do to help the core boot faster I'd like give it a try. As always, any insights shared are greatly appreciated. /Martin --~--~-~--~~~---~--~~ 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: what can I do to speed up bootstrap beforeFilter ?
Also, you shouldn't get DESCRIBE queries, which can slow things down a little, depending on the models used per given page. On Nov 6, 3:00 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: It does not make much difference to the time either way actually. debug 0 results are more often down around 0.06 and debug 1 is more often around 0.08 or maybe up to 0.1 at times. On Nov 6, 8:42 pm, teknoid [EMAIL PROTECTED] wrote: You have debug at 0, I presume? On Nov 6, 2:35 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have been migrating an application to 1.2 and partly because of some threads about performance and benchmarking I have done my own comparisons. Loading up a simple login form for my app (just Auth no ACL) 1.1 is 8-10 times faster. 1.2 quickly catches up on more complete requests with a running session and more data. I was wondering of there was something I could do to my application to speed up Cake's initial overhead? I thought it might be some of my code but the time seem to be lost between bootstrap.php and the beforeFilter. Dropping all components does very little so I am guessing that if any time can be saved it has to be in routing or by some opcode caching. My server has eAccelerator running. Is there any experience of problems using eAccelerator (or APC) with 1.2 or anything like that which could explain the difference? Or , maybe I should say is there anything I may have forgotten to do that would make opcode caching work more efficiently on 1.2? I want to be clear about a few things. 1. I am talking about pretty small numbers here. Hundreds of seconds, not minutes. The total overhead on my server is about 0.06-0.08 sec depending on the mood of the server. 1.1 is usually another 0 down at about 0.008 sec. 1.2 is fast but 1.1 is damn fast, which is slightly annoying :) 2. This is not a big problem for this application on this server but I do have another project where the hardware is being pushed a lot more. This is me learning more about optimization. I am not looking to trim away anything in the core to gain speed but if there is something I can do to help the core boot faster I'd like give it a try. As always, any insights shared are greatly appreciated. /Martin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
