Novelrank is gone

This: I think this underlines, bolds and italicizes that having your entire business built on a platform you have no control over is never a good idea.Jack Welch: Control Your Destiny or Someone Else Will 1) We have a rank tracking service we mostly use for customers’ usage. We had to stop sharing it with our author clients because Amazon would keep blocking itBasically, it’s an hour by hour rank tracking service that shows you exactly how your book does during the promotion (and it keeps going after the promotion). It also includes rank tracking in the individual genres your book is inNot sure why (too much transparency into sales patterns/sales rank movement; for no reason and just because it can; don’t want anyone loading information from their webpages on sales data and trends)Amazon started blocking itTo the point that we had to stop sharing it with author clientsAs soon

Original URL:,266705.0.html

Original article

40M tables in MySQL 8.0 with ZFS

Alexander Rubin

 | September 3, 2018 | 

Posted In: Benchmarks, Big Data, MySQL, MySQL 8.0, ZFS
In my previous blog post about millions of table in MySQL 8, I was able to create one million tables and test the performance of it. My next challenge is to create 40 million tables in MySQL 8 using shared tablespaces (one tablespace per schema). In this blog post I’m showing how to do it and what challenges we can expect.
Once again – why do we need so many tables in MySQL, what is the use case? The main reason is: customer isolation. With the new focus on security and privacy (take GDPR for example) it is much easier and more beneficial to create a separate schema (or “database” in MySQL terms) for each customer. That creates a new set of challenges that we will need to solve. Here is the summary:
Too many files. For each table

Original URL:

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: