Re: MySQL total overheat (somewhat complex database)

2012-08-01 Thread Kurtis Mullins
On Sat, Jul 28, 2012 at 2:44 PM, lubos wrote: > Hello, > > I have a quite sophisticated database with frequently interconnected > tables and on the top level table, Django produces queries like this: > > SELECT `data_schedule`.`id`, `data_schedule`.`process_id`, > `data_schedule`.`hardware_id`, `

Re: MySQL total overheat (somewhat complex database)

2012-07-31 Thread lubos
Hello, I forgot to mention, that this query is generated automatically by Django admin when opening this model admin page. Dne pondělí, 30. července 2012 14:53:10 UTC+2 Cal Leeming [Simplicity Media Ltd] napsal(a): > > Could you provide us with the models.py for this table? Just the model > de

Re: MySQL total overheat (somewhat complex database)

2012-07-30 Thread Cal Leeming [Simplicity Media Ltd]
Could you provide us with the models.py for this table? Just the model definitions will suffice. Can you also provide the snippet of Python code which is generating this SQL Cal On Sat, Jul 28, 2012 at 7:44 PM, lubos wrote: > Hello, > > I have a quite sophisticated database with frequently int

Re: MySQL total overheat (somewhat complex database)

2012-07-30 Thread Joris
If all you do is select data from this set, is by creating the view directly in MySQL, either in 1 or in multiple nested views (subselect or independent views), and using that view as a backend for the django model. This makes optimization easier. -- You received this message because you are

Re: MySQL total overheat (somewhat complex database)

2012-07-28 Thread akaariai
On 28 heinä, 21:44, lubos wrote: > Hello, > > I have a quite sophisticated database with frequently interconnected tables > and on the top level table, Django produces queries like this: > > SELECT `data_schedule`.`id`, `data_schedule`.`process_id`, > `data_schedule`.`hardware_id`, `data_schedule`

Re: MySQL total overheat (somewhat complex database)

2012-07-28 Thread lubos
Yes, they were. On Saturday, July 28, 2012 9:40:42 PM UTC+2, Javier Guerra wrote: > > On Sat, Jul 28, 2012 at 1:44 PM, lubos wrote: > > MySQL, however, isn't able to process it and after few minutes it holds > all > > processor performance. > > that looks like a rather simple star scheme. ma

Re: MySQL total overheat (somewhat complex database)

2012-07-28 Thread Javier Guerra Giraldez
On Sat, Jul 28, 2012 at 1:44 PM, lubos wrote: > MySQL, however, isn't able to process it and after few minutes it holds all > processor performance. that looks like a rather simple star scheme. maybe there are missing indexes... were those tables created by Django? -- Javier -- You received