Wednesday, November 11, 2015

[google-cloud-sql-discuss] Re: setting tx_isolation flag to READ-COMMITTED

Also other important flags we need to set are:

  • innodb_flush_method= O_DIRECT
  • collation_connection= utf8mb4_unicode_ci
  • tx_isolation= READ-COMMITTED
  • innodb_file_format= Barracuda
Some background on our needs, we are a tech company who developed a framework for News aggregation and real time new clustering and filtering. We are processing around 150K news articles a day. Scanning more than 10K websites every 5 min. It is crucial for us to have fast writes on our DB, also due to our clustering algorithms we need "READ-COMMITTED" to avoid dead locks (can't set it at connection set-up too much code to change). utf8mb4_unicode_ci is used to store emoji and the Barracuda file formatted is required for row compression as most of our data is text and can easily be compressed to maintain the DB size moderate.

Thanks
Elia


On Wednesday, November 11, 2015 at 11:33:50 AM UTC+1, Elia Palme wrote:
We have the need to set the default isolation level to READ-COMMITTED. Unfortunately the tx_isolation flag is not stable. How can we set the default isolation level to READ-COMMITTED?

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/5b701beb-d61c-48cf-8cf2-1ba3942826a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment