Hi Sergio, I don't know FloX very well - hence would be good information to know which specific SQL queries are performing bad. Maybe there is room to improve indexing.
Is it also your goal to store every micro-flow into the SQL database? Any chance a more compact aggregation method would fit the bill? Cheers, Paolo On Tue, Apr 27, 2010 at 11:36:50AM -0300, Sergio Charpinel Jr. wrote: > Hi, > > I'm using pmacct 0.12.1 with PostgreSQL 8.4 and FloX. i'm running pmacctd > and nfacctd daemons (probe and collector). > > After 1 day running, I'm getting 1+min to make a query. > Is there any config in pmacct and PostgreSQL that I can do improve this? > > Here is my config in pmacct: > > pmacctd.conf: > daemonize: true > aggregate: src_host, src_port, dst_host, dst_port, proto, tcpflags > plugins: nfprobe > nfprobe_receiver: x.x.x.x > nfprobe_version: 9 > interface: eth1 > > nfacctd.conf: > daemonize: true > pidfile: /var/run/nfacctd.pid > aggregate: src_host,dst_host, src_port, dst_port, proto, tcpflags > plugins: pgsql > sql_table_version: 7 > sql_db: xxxxx > sql_host: x.x.x.x > sql_passwd: xxxxxxx > sql_user: xxxxx > sql_refresh_time: 300 > sql_history: 5m > sql_history_roundoff: m > sql_dont_try_update: true > nfacctd_port: xxxx > nfacctd_ip: xxxx > > In PostgreSQL, I did not change the default config in CentOS 5.4. > > Thanks in advance! > > -- > Sergio Roberto Charpinel Jr. _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
