Hey Tom, On Jul 24, 2009, at 12:01 PM, Tom Anheyer wrote:
hi david, Am Freitag 24 Juli 2009 schrieben Sie:On 24.07.2009, at 11:46, Tom Anheyer wrote:what do you mean by "shrinking the database"? If you're talking aboutstripping the xml files from the agavi config directory then I'dadvice to reconsider that. It will save a little diskspace but won'thave any other effekt. On the downside it will increase maintenance as you'll have to repeat the process each time you update agavi andyou'll have to double check you didn't remove any file that's needed.You are right, but reading the supplemental data cache file costs some time. 1248428583.660914 open ("supplementalData .xml_08137a378e4748b3fe1eedb9148ab38bff300c3b.php", O_RDONLY) = 3 1248428583.670965 close(3) = 0 = 0.010051 seconds I like to reduce this time.Mind me asking why you aren't using an opcode cache?We don't have positive experiences with APC (I don't remeber exacly) someyears ago. But may be they are better now.
We strictly recommend using an opcode cache and spending some effort on tuning the settings. While it is true that opcode caches had some problems when PHP5 was released those issues have long been fixed. Using an opcode cache for agavi applications usually results in performance improvements in the magnitude of factor 5 or more, I have reached performance improvements in the magnitude of factor 10 in some occasions.
Felix -- Felix Gilcher Bitextender GmbH Paul-Heyse-Str. 6 D-80336 München T: +49 89 57 08 15 16 F: +49 89 57 08 15 17 M: +49 172 840 88 28 [email protected] http://bitextender.com/ Amtsgericht München, HRB 174280 Geschäftsführer: David Zülke, Florian Clever
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
