On Sep 28, 3:42 am, Luke Plant wrote:
> But can anyone else think of any gotchas with this change before I
> commit it? It produces a 30% improvement for the benchmark that relates
> to the ticket [3].
Not directly related to this change, but there are at least one part
in Django that will cache
Hi all,
Ticket #14297 [1] suggests changes to LazySettings for performance
improvements. The best solution AFAIC is that __getattr__ triggers a
setup routine on first access, which loads *all* the settings into the
LazySetting object itself. This eliminates the __getattr__ overhead for
all
