> > Could there be some problem, with regards to DB or table locking and > > policyd accessing the tables at same time? > > Well, when LOCK's occur, queries from Policyd -> MySQL will (forcefully) > timeout to prevent any delay. The reason we are using MyISAM instead of > InnoDB is because during testing under really high loads, we found that > InnoDB would not only be slower, but it would actually crash. Perhaps > InnoDB needs to be re-evaluated with the latest release.
The other advantage about MyISAM is the delayed operations in MySQL which makes the queries almost instant. Using InnoDB is going to create delays with the current IO engine in v1 which will slow down all connections. v2 supports both MyISAM and InnoDB in MySQL and maintains multiple connections to the DB. I have v2 currently deployed in production with current SVN HEAD processing 3.6 million messages per day. I'm still pondering about possibly creating a cleanup daemon in addition to the cleanup script to spread the load evenly out during a day. > Are you able to switch your Policyd database over to InnoDB? > (this will require some work, including a few Policyd changes) I wouldn't recommend it due to performance issues. -N
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
