On 24.07.2009, at 11:46, Tom Anheyer wrote:
Hi Felix,Am Freitag 24 Juli 2009 schrieben Sie:Hi Tom, what do you mean by "shrinking the database"? If you're talking about stripping the xml files from the agavi config directory then I'd advice to reconsider that. It will save a little diskspace but won'thave any other effekt. On the downside it will increase maintenance asyou'll have to repeat the process each time you update agavi and you'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.661064 read(3, "<?php\n\n// This is a compiled Aga"..., 65536) = 65536 1248428583.662156 read(3, "<?php\n\n// This is a compiled Aga"..., 65536) = 65536 1248428583.664770 read(3, "kendEnd\' => 1,\n ),\n ),\n "..., 65536) = 65536 1248428583.667438 read(3, " \'currency\' => \'INR\',\n "..., 65536) = 65536 1248428583.670192 read(3, "rica/Noronha\' => \'BR\',\n \'Am"..., 65536) = 95981248428583.670581 read(3, "", 65536) = 0 1248428583.670698 read(3, "", 65536) = 0 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? - David
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
