Am Tuesday, October 2, 2007, 12:45:33 AM beglückte uns Tristan ([EMAIL PROTECTED]) mit folgendem Kommentar:
> Will using a database backend to store flowdata help improve query > times? Has anyone experimented with this? We are extending our accounting tool from the state of "save inbound and outbound sum traffic per IP per day in database" (which worked fine for accounting purposes) to "store each flow in database to do drill down statistics". As not beeing a major carrier, we have around 2 Gigs of database space (with just one index) for incoming and outgoing traffic each, with a target of holding at least 90 days of data. After testing with PostgreSQL (which proved unacceptable mass insertion times even with all the tipps moving around on the internet), we were going back to mySQL, testing the new 5.1beta release with partition support (each day a partition, so we have only 2 GB of data to search when searching within a given day), and I must admit I didn't expect that it works like a charme for the price. Yeah, maybe with a better database it works even better, but I didn't get the budget for this... ;-) Jens ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
