It's one per file access as far as I know. This means that if all your CSS and icons lie in the same hierarchy where your .htaccess is, they will require a read of the .htaccess.
In Chamilo classic, we use an .htaccess at the courses/ directory level (the one that contains all the course contents) to avoid unprivileged access to documents, but we avoid having it at the root level so that icons/css/js can be served without it. Of course, this all falls down to tuning, but I wanted to mention it. Also worth mentioning is that I started writing an optimization guide for Chamilo classic inside the documentation folder. It's pretty basic but following can generally give you boosts of 200 to 300%: http://chamilodev.beeznest.com/documentation/optimization.html It's probably worth doing something similar in 2.0 were every developer can add his/her observations progressively while experimenting with small optimization things. Yannick El jue, 26-05-2011 a las 10:00 +0200, Systho escribió: > You're right VirtualHost (or, more often <Directory> on a dev machine) > is more performant but not always accessible. > > Is the htaccess file read once per request or once per file access ? in > the first case, I don't think it's *that much* performance loss but in > the second case it would probably have a real impact. > > Systho > > On 26/05/11 00:36, Yannick Warnier wrote: > > Hi all, > > > > .htaccess files are a performance killer, particularly at the root of a > > web application (because they apply, by default, to all sub-directories > > and because they are read *every* time there is an access to any file on > > the system). Even so, they are still widely used because they're easy, > > but I think somehow we should provide some kind of documentation > > indicating that the setting can be configured inside an Apache's Virtual > > Host very easily like so: > > > > ... > > php_value output_buffering Off > > </VirtualHost> > > > > Virtual hosts configuration files are read only once at Apache's reload > > and cover the whole site hierarchy without further read. > > > > Regards, > > > > Yannick > > E > > l mié, 25-05-2011 a las 19:03 +0200, Hans De Bisschop escribió: > >> Hi Philippe, > >> > >> No problem whatsoever for me. Connected to that I think the actual > >> settings-check during the installation can be safely removed ... we > >> could keep it as advise, but that should be it. > >> > >> Hans > >> > >> On 25/05/2011 16:36, Philippe Van Eerdenbrugghe wrote: > >>> Hi all > >>> > >>> since most users will use an apache server with php loaded as a > >>> module, what do you think of providing an .htaccess file containing > >>> the line : > >>> > >>> php_flag output_buffering Off > >>> > >>> at the root of chamilo for all the users who can't / don't want to > >>> edit their php.ini file ? > >>> > >>> I personally use that feature locally since I don't want all my > >>> projects to shut down output_buffering and it works quite well. > >>> > >>> Systho > >>> > >>> _______________________________________________ > >>> Dev mailing list > >>> [email protected] > >>> http://lists.chamilo.org/listinfo/dev > >> _______________________________________________ > >> Dev mailing list > >> [email protected] > >> http://lists.chamilo.org/listinfo/dev > > > > _______________________________________________ > > Dev mailing list > > [email protected] > > http://lists.chamilo.org/listinfo/dev > > _______________________________________________ > Dev mailing list > [email protected] > http://lists.chamilo.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] http://lists.chamilo.org/listinfo/dev
