Thanks Karen, that was just the ticket.
On Jan 29, 10:52 pm, Karen Tracey wrote:
> On Thu, Jan 29, 2009 at 5:49 PM, Tipan wrote:
> > I'll go ahead as planned on the Django update and see if this delivers
> > any improvements. With regards to your suggestion of using the raw id
> > field, is thi
On Thu, Jan 29, 2009 at 5:49 PM, Tipan wrote:
> I'll go ahead as planned on the Django update and see if this delivers
> any improvements. With regards to your suggestion of using the raw id
> field, is this a Django option, or did you mean changing the FK to
> using a simple ID field. I've been
>
> Without specifics, it's a little difficult to say for certain, but one
> of the reasons for the switch to newforms and newforms-admin was to
> eliminate some very expensive querying behavior in the manipulators
> behind forms. This wasn't a matter of one big query that was expensive
> - but yo
On Thu, Jan 29, 2009 at 7:41 AM, Tipan wrote:
>
> Can anyone suggest some areas to explore to improve the response time
> on the Admin. We're currently on release 7476 (pre new forms admin),
> but due to go to the latest development release next week, although
> I'm not sure how significant this
On Wed, Jan 28, 2009 at 5:41 PM, Tipan wrote:
>
> We're running several Django sites on 3 dedicated servers with (1 app,
> 1 media and 1 data). The sites generally run pretty quickly for users.
> We are using db caching (we'll be moving to mem_cached in due course)
> on most views other than thos
We're running several Django sites on 3 dedicated servers with (1 app,
1 media and 1 data). The sites generally run pretty quickly for users.
We are using db caching (we'll be moving to mem_cached in due course)
on most views other than those showing specific user data. The site
has about 90,000 r
6 matches
Mail list logo
