On Wed, Jan 21, 2009 at 10:28:13AM +1100, Stephen Vaughan wrote: Hi Stephen, I'd need to understand a bit more about what you are doing in order to suggest a solution to that problem. But to answer your question, no perdition doesn't support storing regexes in MySQL directly. I suspect that either adding a specialised popmap, or to write a daemon that returns results to the daemon map. -- Simon Horman VA Linux Systems Japan K.K., Sydney, Australia Satellite Office H: www.vergenet.net/~horms/ <http://www.vergenet.net/%7Ehorms/> W: www.valinux.co.jp/en

On Wed, Jan 21, 2009 at 12:48:31PM +1100, Stephen Vaughan wrote: to about is Hi Stephen, I'm a little surprised that perdition is slow in the way that you describe, but I'm not surprised that it is slow in some way with your configuration. When I wrote the popre code (which was rather a long time ago) I wasn't thinking in terms of it scaling to 13,000+ entries. The implementation is rather simple and works in two parts as follows: on load or reload: Run through the popmap.re file and for each entry compile it as a regex All tresultsand store the result in an array on lookup: Run through the array in order, checking each regex in turn. Return when a match is fine. So basically both load/reload and lookup is O(n), where n=13,000+. Clearly not sastifactory. Do you actually need the regex? If you are just mapping domain names to IP addresses, then I think that you can use the MySQL, PostgreSQL, ODBC, BDB, GDBD, LDAP or even NIS module. The trick is to set the query key to so that only the domain name supplied by the username is passed to the db module to perform the lookup. This is done by setting query_key in the perdition configuration file or on the command line: query_key=\d -- Simon Horman VA Linux Systems Japan K.K., Sydney, Australia Satellite Office H: www.vergenet.net/~horms/ <http://www.vergenet.net/%7Ehorms/> W: www.valinux.co.jp/en

On Wed, Jan 21, 2009 at 03:42:15PM +1100, Stephen Vaughan wrote: Hi Stephen, I suspect MySQL would be faster but that for a table of that size LDAP sould still be reasonable.

Hello, On Wed, 21 Jan 2009 09:41:10 +0200 Janne Pikkarainen wrote: Same here with pretty much the same amount of users and time frame. The L in LDAP does mean something after all and if properly configured will beat the pants off a generic DB like MySQL.

ok well I've setup mysql, it all seems ok except the query is wrong. mysql logs are showing: 090121 16:12:48 61 Connect perdition@localhost on dbPerdition 61 Query select servername,user,port from tblPerdition where servername='d' 61 Quit I've added query_key=\d to perdition.conf Any ideas?