2014-05-15 14:26 GMT+02:00 Antonio Fernández Pérez
antoniofernan...@fabergroup.es:
Hi,
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we
- Original Message -
From: Manuel Arostegui man...@tuenti.com
Subject: Re: Big innodb tables, how can I work with them?
noSQL/table sharding/partitioning/archiving.
I keep wondering how people believe that NoSQL solutions magically don't need
RAM to work. Nearly all of them slow
2014-05-19 11:49 GMT+02:00 Johan De Meersman vegiv...@tuxera.be:
- Original Message -
From: Manuel Arostegui man...@tuenti.com
Subject: Re: Big innodb tables, how can I work with them?
noSQL/table sharding/partitioning/archiving.
I keep wondering how people believe that NoSQL
What kind of queries is this table serving? 8GB is not a huge amount of
data at all and IMO it's not enough to warrant sharding.
On Thu, May 15, 2014 at 1:26 PM, Antonio Fernández Pérez
antoniofernan...@fabergroup.es wrote:
Hi,
I have in my server database some tables that are too
Hi,
Thanks for your replies.
In our case, we can't implement NOSQL solution. Thats requires modify/check
all our application and all services (Including FreeRADIUS that I'm not
sure if it's compatible).
Andrew, I have heard about people that has a lot of data, more than me. I
know that MySQL
Hi,
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we make an
authentication process with RADIUS users (AAA protocol) to determine if one
user can
Am 15.05.2014 14:26, schrieb Antonio Fernández Pérez:
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we make an
authentication process with RADIUS
