Re: Session Benchmarks

2005-06-17 Thread Nicolas Lehuen
2005/6/17, Jim Gallacher <[EMAIL PROTECTED]>: > It really would be helpful if everyone could read minds. Maybe we could > put a mind-reading feature in 3.3? :) Although that might push 3.3's > release back to 2020. And could it be made thread safe... And if it could be made language-neutral, too,

Re: Session Benchmarks

2005-06-17 Thread Nicolas Lehuen
2005/6/17, David Fraser <[EMAIL PROTECTED]>: > I don't know how it could be made good performance-wise, but it would be > great to have a generic database session store that you could pass a > Python DB-API connection object to. Of course, that would be difficult > to configure in the same way as t

Re: Session Benchmarks

2005-06-17 Thread Nick
Gregory (Grisha) Trubetskoy wrote: I'm a little concerned about staying focused on closing the last bugs so that we get to a point where a release can be made, since there hasn't been one in such a long time... +1 on that Nick

Re: Session Benchmarks

2005-06-17 Thread Jim Gallacher
Gregory (Grisha) Trubetskoy wrote: On Fri, 17 Jun 2005, Jim Gallacher wrote: Any objection to just a SqlSession base class? May be - it depends on how complex it becomes. Any attempts I've to generalize SQL/DB stuff tend to become a mess since there are no firm standards in this area, s

Re: Session Benchmarks

2005-06-17 Thread Jim Gallacher
Gregory (Grisha) Trubetskoy wrote: On Fri, 17 Jun 2005, Jim Gallacher wrote: I was thinking we'd still use the current global locking scheme, but keep the file open between requests. Not sure if this would be robust or just asking for dbm file corruption though. I'm pretty sure it won't wo

Re: Session Benchmarks

2005-06-17 Thread Gregory (Grisha) Trubetskoy
On Fri, 17 Jun 2005, Jim Gallacher wrote: Any objection to just a SqlSession base class? May be - it depends on how complex it becomes. Any attempts I've to generalize SQL/DB stuff tend to become a mess since there are no firm standards in this area, so this just may be something for the

Re: Session Benchmarks

2005-06-17 Thread Gregory (Grisha) Trubetskoy
On Fri, 17 Jun 2005, Jim Gallacher wrote: I was thinking we'd still use the current global locking scheme, but keep the file open between requests. Not sure if this would be robust or just asking for dbm file corruption though. I'm pretty sure it won't work, I think you cannot have a dbm ope

Re: Session Benchmarks

2005-06-17 Thread Jim Gallacher
Gregory (Grisha) Trubetskoy wrote: On Fri, 17 Jun 2005, Nicolas Lehuen wrote: As for the MySQL implementation I'd stay away from anything vendor-specific in mod_python, because then the question becomes why not a postresql, why not oracle, etc. Any objection to just a SqlSession base c

Re: Session Benchmarks

2005-06-17 Thread Jim Gallacher
Gregory (Grisha) Trubetskoy wrote: On Fri, 17 Jun 2005, Jim Gallacher wrote: Brain Wave It just occured to me that the performance problem may be related to opening and closing the dbm file for every record insertion. Adjusting the test so that the file is only opened once, I get

Re: Session Benchmarks

2005-06-17 Thread Gregory (Grisha) Trubetskoy
On Fri, 17 Jun 2005, Nicolas Lehuen wrote: As for the MySQL implementation I'd stay away from anything vendor-specific in mod_python, because then the question becomes why not a postresql, why not oracle, etc. Grisha

Re: Session Benchmarks

2005-06-17 Thread Gregory (Grisha) Trubetskoy
On Fri, 17 Jun 2005, Jim Gallacher wrote: Brain Wave It just occured to me that the performance problem may be related to opening and closing the dbm file for every record insertion. Adjusting the test so that the file is only opened once, I get O(1), and a great speed boost: 0.2

Re: Session Benchmarks

2005-06-17 Thread Jim Gallacher
Nicolas Lehuen wrote: 2005/6/17, David Fraser <[EMAIL PROTECTED]>: I don't know how it could be made good performance-wise, but it would be great to have a generic database session store that you could pass a Python DB-API connection object to. Of course, that would be difficult to configure in

Re: Session Benchmarks

2005-06-17 Thread Jim Gallacher
Nicolas Lehuen wrote: Hi Jim, You've done a pretty impressive work here. What surprises me is the O(n) behaviour on DBM and FS. This seems to mean that indexes (or indices, if you prefer) ar not used. ext2/ext3 uses a linked list to access files, hence O(n) when adding a file. For DBM, well,

Re: Session Benchmarks

2005-06-17 Thread David Fraser
Nicolas Lehuen wrote: Hi Jim, You've done a pretty impressive work here. What surprises me is the O(n) behaviour on DBM and FS. This seems to mean that indexes (or indices, if you prefer) ar not used. For DBM, well, if BDB could not handle indexes, this would be big news. Are you 100% sure tha

Re: Session Benchmarks

2005-06-17 Thread Nicolas Lehuen
Hi Jim, You've done a pretty impressive work here. What surprises me is the O(n) behaviour on DBM and FS. This seems to mean that indexes (or indices, if you prefer) ar not used. For DBM, well, if BDB could not handle indexes, this would be big news. Are you 100% sure that the Berkeley implementa