I am wondering why the pool_size is set to 0 by default http://web2py.com/books/default/chapter/29/06#Connection-pooling Which are the side effect of having something greater than 0? Is not worth to have it set for example as 5 by default?
paolo On Thursday, March 14, 2013 2:47:56 PM UTC+1, Niphlod wrote: > > those are more or less in line with my "old" tests on my home rig. > If you don't specify a pool argument, every request needs to establish a > connection with the db. > > On Thursday, March 14, 2013 2:32:58 PM UTC+1, Daniel Gonzalez wrote: >> >> Great, thanks Niphlod! >> >> Now the setup times have been reduced to the <3ms (with some cases of >> >3ms, and even less over 10ms). I would say, discarding the initial pool >> setup, the average is around 4 ms, with some spikes around 10ms (these are >> not accurate stats) >> >> Anyway, looks like an improvement. >> >> On Thursday, March 14, 2013 2:13:51 PM UTC+1, Niphlod wrote: >>> >>> pool ? >>> >>> On Thursday, March 14, 2013 1:16:25 PM UTC+1, Daniel Gonzalez wrote: >>>> >>>> This codes in the model takes between 5ms and 24ms to complete: >>>> >>>> WEB2PY_DAL_STORAGE="postgres://myuser:mypass@localhost:5432/mydb" >>>> db = DAL(WEB2PY_DAL_STORAGE, migrate_enabled=False, lazy_tables=True) >>>> >>>> I am in a laptop with: >>>> >>>> - 2 cores, 3300 bogomips/core >>>> - 4 GB >>>> - linux 2.6.32-5-686 >>>> >>>> Is this expected? >>>> >>>> Thanks, >>>> Daniel >>>> >>> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
