I guess I would still recommend that you not get too fancy. Your data rate is 50 plants, 8000 records each, for a total of 400k records per day. I have a MySQL table that added 500k records in the last 24 hours, and it's fine. It's just an ordinary Innodb table, with no special optimizations. At these data rates, at least in our environment, the challenges lie elsewhere (nginx throughput, Django throughput, etc). Our datrabase has a handful of tables in the 60-million-row neighborhood, and the db as a whole manages almost 80Gb of data.
Are you sure you have a problem to solve here? Relational databases really are quite good at what they do, it's unusual cases where you have to help them with partitioning and the like. --Ned. Alessandro Ronchi wrote: > One simple solution for my problem is table partitioning. Both MySQL > and PosgreSQL can handle that. > On PGSQL I can create a master table for my model and one partition > for every value of a master key. It should be great. > > Do you think it's possible to handle a child table creation (also with > a PGSQL command without ORM) on a save of a model? The query and > inserts should be transparent, and so I could use django for > everything. > > > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
