On Friday, March 18, 2011 08:33:30 am Paul McNett wrote: > On 3/18/11 8:19 AM, John Fabiani wrote: > > Hi, > > The settings_override.py contains the setting > > fastNameSet = False > > > > I have never changed this setting. I currently have a client wondering > > why it takes so long for a form to appear (we are talking only ~10 > > seconds). At first I considered that the reason was the access to the > > data. However, I discovered that most of the time is not the access to > > the data - total time accessing data as reported from postgres logs is > > less than a second. So in looking for a little more performance I was > > wondering if anyone has actually seen a difference in opening > > performance by changing the setting from False to True. I don't use > > 'Name' for my objects - only 'RegID'. So I don't see any harm on the > > surface. > > > > The doc suggest that I wrap each object call and set the 'setting' - but > > since I'm talking about lot's of code I don't want to do that. > > > > Looking for a little advise - thanks in advance. > > Why don't you write up a few quick test cases, some that set the name > property, some that don't; some that use fastNameSet, some that don't, > when instantiating something like 200 objects... > > I can't imagine that writing and analyzing those tests would take longer > than 20 minutes, and that sharing the results would take longer than 5... > > ;) > > Paul
On windows I see little to no difference - on linux there appears to be a measurable difference. However, I do not know if there was any caching taking place. I'm going just set it to true and not worry about it. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
