> This means I can do things like easily drop older tables if I run out of >> disk space. It also means that I can fadvise the most recent tables and >> force them into table cache. >> > > If you have to use fadvise to do this, you are almost certainly Doing It > Wrong. >
possibly.. fincore is also useful. This way you can see the cache % of each file… if I'm doing something funky the older files should not be in cache at all. and fadvise dontneed is your friend too. > > >> But what's the max number of tables? If I'm doing hourly tables and have >> 30 days of them this would be 720 individual tables. >> > > Probably pushing it. > > What are the bottlenecks here ? Is this an HDD issue because we're running them on SSD. I agree that that would be significant on HDD ... -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
