Re: Poor Performance for Form Rendering In Django 1.11

t; > > > > > > > > *From:* django...@googlegroups.com [mailto: > django...@googlegroups.com ] *On Behalf Of *John > *Sent:* Monday, December 10, 2018 9:19 AM > *To:* Django users > *Subject:* Re: Poor Performance for Form Rendering In Django 1.11 > >

RE: Poor Performance for Form Rendering In Django 1.11

Performance for Form Rendering In Django 1.11 Yes, the form has about a dozen selects, with two in particular being larger - the country and the currency fields - that probably have a couple hundred options each. I have since removed those two fields which leaves about 10 selects with about 80

Re: Poor Performance for Form Rendering In Django 1.11

Yes, the form has about a dozen selects, with two in particular being larger - the country and the currency fields - that probably have a couple hundred options each. I have since removed those two fields which leaves about 10 selects with about 80 options total. While these numbers fluctuate

Re: Poor Performance for Form Rendering In Django 1.11

On Mon, Dec 10, 2018 at 6:29 AM John Lehmann wrote: > So my takeaway from what you are saying is that no one is running a > production site with a Django select field to render a country or currency > option (e.g., django-countries or django-money), because either of these > would have well over

Re: Poor Performance for Form Rendering In Django 1.11

Hi James, Thank you for the input! So my takeaway from what you are saying is that no one is running a production site with a Django select field to render a country or currency option (e.g., django-countries or django-money), because either of these would have well over a hundred entries (and my

Re: Poor Performance for Form Rendering In Django 1.11

On Mon, Dec 10, 2018 at 5:31 AM John Lehmann wrote: > I am still hoping however for someone to explain to me why the default > renderer cannot handle my use case, such as that a few hundred inputs is > too many, or that I am doing something else improperly. Surely this kind > of a change would n

Re: Poor Performance for Form Rendering In Django 1.11

Hi Simon, thanks for the response. I am still hoping however for someone to explain to me why the default renderer cannot handle my use case, such as that a few hundred inputs is too many, or that I am doing something else improperly. Surely this kind of a change would not be made to the framewor

Re: Poor Performance for Form Rendering In Django 1.11

Hello John, Did you try switching to the Jinja2 form renderer[0] to see if it helps? I've not tried it myself but I heard it makes a significant difference. Cheers, Simon [0] https://docs.djangoproject.com/en/2.1/ref/forms/renderers/#jinja2 Le vendredi 7 décembre 2018 08:30:48 UTC-5, John a éc

Poor Performance for Form Rendering In Django 1.11

My site has a navbar with an advanced search widget (beside the search field), which renders on every page. For each request, a context_processor creates the form so it can be available on that page in the navbar. This form has about a dozen selects with a total