Optimal DB and configuration for proxies

[Jason]

I'm starting to do a lot more with proxies, mainly snmp monitoring and VMware monitoring, but so far I've always stuck with the stock sqlite3 database.

Has anyone used mysql or postgres for proxies and is there much of a performance difference?

At the moment the proxies have between 10 and 80 values per second although some of them are about to get significantly more. Generally we build our proxies on stripped down centos 6 virtuals.

We've found that disabling bulk snmp requests seems to help on a lot of kit, but can still end up with a large snmp queue and increasing timeout or number of pollers doesn't really seem to help this much. snmpwalk of the devices in question always returns all the data quickly.

[kloczek]

Has anyone used mysql or postgres for proxies and is there much of a performance difference?

sqllite on every batch of changes must write new whole file with database content to the file system. So this is why whit growing number of items sqllite is more and more less effective. However in case of small proxy sqllite is better/faster than mysql/postgresql

In case of using SQL engine there is no such needs so mysql or postgresql is way better.
Because mysql is much simpler engine and zabbix proxy or server it is typical warehouse DB my private recommendation is mysql.

[wdijkerman]

I almost always use MySQL as database (For every tool I can choose an database). It is something I have experience with, so this would be for me the logical solution. But someone else can have the same thing for PostgreSQL. I wouldn't use sqlite or Oracle. Sqlite for very small environments is maybe possible, but I never used sqlite. Oracle is expensive, so ...

[Jason]

I've put one of my proxies with about 70 vps on mysql db to see how it performs. So far seems ok, but no real difference in load/performance noticed.