Re: Database optimalisation and rotation.

Yes it does use transactions.

On Wed, 30 Jan 2008 6:42 am, Konrad Kosmowski wrote:
> Any thoughts/hints/suggestions on following:
>
> 1. Database optimisation - I will probably soon have quite big Prelude
> database (I estimate more than 20 gigabytes). How to optimize MySQL
> server for such database? I mean any tweaks specific to
> libpreludedb-mysql operation. I've looked (quickly though) into the
> code and haven't found any InnoDB specific stuff (like transactions)
> but schema create statements use InnoDB table type. Wouldn't it be
> more efficient to use MyISAM? Or maybe I am totally wrong and
> libprelude uses transactions?
>
> 2. How to rotate events in database? For example I wish to store only
> data from last week since more data will crawl my database server to
> death. How to periodically (f.e. each night) purge the database from
> data older than N days?
> _______________________________________________
> Prelude-user site list
> [email protected]
> http://www.prelude-ids.org/mailman/listinfo/prelude-user
___________________________________________
The average person does a lot of work in the name of laziness!
Save youre self the effort by doing it right the first time.
Do it with free speech software.
_______________________________________________
Prelude-user site list
[email protected]
http://www.prelude-ids.org/mailman/listinfo/prelude-user