I know it's not big by some standards, and we have done a lot of tuning. Really more then speed issues, our larger issues are administrative - we need 24x7 uptime and the tables are so large we cannot do any alters as they take days to run. Similarly, a restore can take a week. So we want to look at other dbs that could mitigate those issues.
On Fri, Sep 29, 2017 at 5:25 AM, Avraham Serour <[email protected]> wrote: > That doesn't sound that big. > Maybe you can tune mysql, but I have worked with postgres handling more than > that, it works fine without tuning, I changed a couple of settings (like > work_mem) and improved > > On Fri, Sep 29, 2017 at 4:48 AM, Larry Martell <[email protected]> > wrote: >> >> I am taking about using hbase as a db for Django. My use case is that a >> have a Django app and the data in mysql has grown to the point where >> performance has greatly suffered. >> >> We have around 2TB of data with some very wide tables with many millions >> of rows. So I am beginning my research into how to improve performance. >> >> On Thu, Sep 28, 2017 at 9:41 PM Vivek Shrivastava >> <[email protected]> wrote: >>> >>> Are you asking HBase as database for Django or accessing HBase from >>> Django? The popular framework Hue http://gethue.com/ is based on Django >>> only.. >>> >>> On Thu, Sep 28, 2017 at 9:34 PM, Larry Martell <[email protected]> >>> wrote: >>>> >>>> Has anyone ever used any big data solutions, such as hbase, with django? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACwCsY7Pet-%3DEofWhENewxV7kBG7voE3jAuymjQ2EzdwDZLBeg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
