Re: [web2py] Performance overhead when making languages not writable

2012-10-16 Thread Massimo Di Pierro
I added this current.T.is_writable = False or True I do not think this adds any performance penalty because writes should not happen anyway. If they happen, there is already a big performance hit. On Tuesday, 16 October 2012 06:21:40 UTC-5, Massimo Di Pierro wrote: > > Fran is right. We need t

Re: [web2py] Performance overhead when making languages not writable

2012-10-16 Thread Niphlod
I'm a little bit uncertain about this. We're struggling to make web2py somewhat faster but then we're incline to drop in "faulty checks for every request" just to support run-time configs Can we think about something like global_settings_per_app that is set (and stored) at the first request

Re: [web2py] Performance overhead when making languages not writable

2012-10-16 Thread Massimo Di Pierro
Fran is right. We need this configurable per app, not global On Tuesday, 16 October 2012 05:32:19 UTC-5, Fran wrote: > > On 15 October 2012 20:17, Vladyslav Kozlovskyy > > > wrote: > > sure, it's a right decision :) > > Thanks for adding this, however I actually don't see this as ideal no

Re: [web2py] Performance overhead when making languages not writable

2012-10-16 Thread Fran Boon
On 15 October 2012 20:17, Vladyslav Kozlovskyy wrote: > sure, it's a right decision :) Thanks for adding this, however I actually don't see this as ideal now. Here it is read only once - at web2py startup. I'm not sure how or where I would set this. Ideally I'd like to control this setting withi

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Massimo Di Pierro
In trunk! Thank you. On Monday, 15 October 2012 16:22:30 UTC-5, dbdeveloper wrote: > > Done > > У пн, 2012-10-15 у 13:34 -0700, Massimo Di Pierro пише: > > OK. send me a patch. :-) > > On Monday, 15 October 2012 12:44:48 UTC-5, Fran wrote: > > On 15 October 2012 18:36, Vladyslav Kozlovskyy wrote

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Vladyslav Kozlovskyy
Done У пн, 2012-10-15 у 13:34 -0700, Massimo Di Pierro пише: > OK. send me a patch. :-) > > On Monday, 15 October 2012 12:44:48 UTC-5, Fran wrote: > > On 15 October 2012 18:36, Vladyslav Kozlovskyy > wrote: > > We have [is_gae] variable in [gluon/languages.py] to avoid

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Massimo Di Pierro
OK. send me a patch. :-) On Monday, 15 October 2012 12:44:48 UTC-5, Fran wrote: > > On 15 October 2012 18:36, Vladyslav Kozlovskyy > > > wrote: > > We have [is_gae] variable in [gluon/languages.py] to avoid writting > dicts in > > Google AppEngine. > > All we need is to make such replacement

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Vladyslav Kozlovskyy
sure, it's a right decision :) У пн, 2012-10-15 у 18:44 +0100, Fran Boon пише: > On 15 October 2012 18:36, Vladyslav Kozlovskyy wrote: > > We have [is_gae] variable in [gluon/languages.py] to avoid writting dicts in > > Google AppEngine. > > All we need is to make such replacement in [gluon/lan

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Fran Boon
On 15 October 2012 18:36, Vladyslav Kozlovskyy wrote: > We have [is_gae] variable in [gluon/languages.py] to avoid writting dicts in > Google AppEngine. > All we need is to make such replacement in [gluon/languages.py]: > replace > 38 is_gae = settings.global_settings.web2py_runtime_gae > with > 3

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Vladyslav Kozlovskyy
Hi all! We have [is_gae] variable in [gluon/languages.py] to avoid writting dicts in Google AppEngine. All we need is to make such replacement in [gluon/languages.py]: replace 38 is_gae = settings.global_settings.web2py_runtime_gae with 38 is_gae = settings.global_settings.web2py_runtime_gae or s

Re: [web2py] Performance overhead when making languages not writable

2012-10-15 Thread Vinicius Assef
I'd like to have a global (app wide) option to not override my language files. On Mon, Oct 15, 2012 at 1:47 PM, Fran wrote: > On my Production servers I don't like the languages/* files to be writable - > I prefer to keep these files part of the application's version control & > translated outs

[web2py] Performance overhead when making languages not writable

2012-10-15 Thread Fran
On my Production servers I don't like the languages/* files to be writable - I prefer to keep these files part of the application's version control & translated outside the application. Currently this leads to a performance overhead as there are many times that write_dict() is called and so glu