What I call "rendering templates" is only the view part of the MVC
model. Waiting for XML and reading them is definitly between Model
(beans) and Controler (actions and readers). But our templates are a
bit complex : depending on the offer size, we have 12 different main
templates to render an offe
> In the meantime, we have moved forward on our timer method and we
> discovered that rendering templates took us about 200ms. Don't you
> think this is huge ?
> Thanks anyway !
=
Does this include the time to wait for the XML data source?
On my dev machine it takes about 17 ms to process fact
AllowOverride was already set to none.
Database functionnality is set to off in settings.yml.
But I've tried to tweak some APC configuration keys with :
--
# Do not need to check for file changes : we only update them with a
new release deployed in another versionne
On Nov 16, 7:17 pm, Remi wrote:
> -> we don't use any .htaccess file : everything goes directly to an
> "httpd.conf"
=
Also have
AllowOverride none
in apache config to not search for .htaccess files.
> -> we don't use ORM since we don't use databases : only Webservices
=
Make sure you dis
Apc settings :
http://www.php.net/manual/en/apc.configuration.php#ini.apc.stat
Then you should install xhprof to find the bottleneck.
On Tue, Nov 16, 2010 at 6:17 PM, Remi wrote:
> -> we don't use any .htaccess file : everything goes directly to an
> "httpd.conf"
> -> we don't use ORM since we
-> we don't use any .htaccess file : everything goes directly to an
"httpd.conf"
-> we don't use ORM since we don't use databases : only Webservices
-> how can I be sure that APC is well configured ? Do I have a way to
easily check if APC is working well ?
-> from what I heard, memcache and APC are
-> we only use routing.yml to load our routes
-> we don't use session (our old frontend was not session-less and it
was a real pain in the ass !)
-> we do as few io as possible : only to write a few logs (2 lines in
one single file for each request)
-> our source code is not mounted via NFS
-> we'v
Hi,
we already tried to add timers (using sfTimerManager) on some key
algorithms (routing, culture detection, tree recursive searches, ...)
and we didn't find anything off the chart. It seems that everything is
slower than we expected but not too much, pointing us to an algorithm
issue.
I will try
Some other suggestions:
- avoid .htaccess - move rewrite rules in the Apache configuration.
- avoid the ORM - if you do access the database use plain SQL to
manipulate the data.
- make sure APC is configured correctly (so that it caches large PHP
files, such as the ones generated by the routing)
