Showing entries 15993 to 16002 of 44964
« 10 Newer Entries | 10 Older Entries »
First sysbench results comparing Amazon AWS RDS instances

RDS instance details

  • sysbench seeded 100Gb database and then snapshotted
  • 1Tb of RDS storage for the database
  • RDS MySQL 5.5.27
  • Default my.cnf RDS configuration except (find the full 'show global variables' output at the end of this post)
    • performance_schema is enabled
    • innodb_flush_logs_at_trx_commit = 0
  • provisioning an RDS instance for each instance size / PIOPS configuration from the seeded database. (10 in total) 


Test details

  • Amazon RDS 
  • Within an AWS VPC
  • US-East



First warm up innodb by running sysbench with options

  • oltp table size 1000000000
  • max-requests 0
  • max-time 300 (5 minute warm up)
  • oltp test mode complex
  • oltp index …
[Read more]
The state of MySQL client libraries

Those who’ve been around the MySQL world are probably aware of the much-discussed topics of GPL licensing, dual licensing, and in particular, licensing of the client libraries (also called connectors or drivers) and the FOSS exception to that licensing. This is newly relevant with the announcement of a permissively-licensed MySQL-compatible client library for MariaDB.

The difference is that this time there’s been some question about the provenance and history of the source code. Some people asked me about this. Some of them were aware of a relatively obscure detail: there’ve been permissively licensed MySQL client libraries for years, in the form of libdrizzle, a BSD-licensed library for the Drizzle fork of MySQL.

Here are some of the thoughts that seemed to be going through peoples’ minds:

  • This changes everything, …
[Read more]
OblakSoft Cloud Storage Engine Newsletter, December 2012

ClouSE version 1.0b.1.6 is released

OblakSoft is pleased to announce the release of ClouSE version 1.0b.1.6.  In this release we fixed some of the known ClouSE Beta limitations as well as performance and functional bugs reported by our users.

Here is the summary of changes that are included into 1.0b.1.6:

  • Support for latest MySQL 5.5

Now ClouSE supports MySQL thru 5.5.29.  To keep the distribution small, we don’t build binaries for MySQL prior to 5.5.19 anymore.  If you need one, please contact us.

  • DECIMAL keys support

Now ClouSE supports using DECIMAL fields in keys.  Previously neither the primary key nor indices could include DECIMAL fields.  This fixes the following Beta limitation: DECIMAL fields cannot …

[Read more]
The state of MySQL client libraries

Those who’ve been around the MySQL world are probably aware of the much-discussed topics of GPL licensing, dual licensing, and in particular, licensing of the client libraries (also called connectors or drivers) and the FOSS exception to that licensing. This is newly relevant with the announcement of a permissively-licensed MySQL-compatible client library for MariaDB. The difference is that this time there’s been some question about the provenance and history of the source code.

MySQL Connector/Python 1.0.8 available for download

Last week we made a maintenance release for MySQL Connector v1.0 available. The announcement can be read in the MySQL forums and the history log is available online.

Connector/Python v1.0.8 does not introduce anything new, it only comes with bug fixes. Some are quite important and it’s probably good to upgrade.

Please use the MySQL Bugs website to report any problem.

Some useful links:

[Read more]
Merry Christmas
mysql --silent -niGHt -e "SELECT GROUP_CONCAT(val ORDER BY id SEPARATOR ' ') AS Greeting FROM mysql.greeting"
Greeting
Merry Christmas and Happy New Year
See you in 2013

mysql is the MySQL Command Line Client – my favourite tool when using MySQL. It is available on all platforms where you can install MySQL and is part of a standard installation. As you can see there are many options, including the -H which causes the output to be HTML formatted. Ok, I cheated here and created the table manually as my blog editor escapes HTML code – the actual output looked like:

<TABLE BORDER=1><TR><TH>Greeting</TH></TR><TR><TD>Merry Christmas and Happy New Year
See you in 2013</TD></TR></TABLE>

[Read more]
OurSQL Episode 121: Fun with text files

This week we discuss manipulating text data and the CSV storage engine. Ear Candy is Venn Diagrams visually showing joins, and At the Movies is about how to retain your individuality while being on a team.

Events
FOSDEM 2013 is taking place in Brussels, Belgium Sat Feb 2 - Sun Feb 3rd. Call for papers for the MySQL & Friends room closes December 21st.

Northeast LinuxFest is happening at Harvard University, Cambridge MA Saturday March 16th and Sunday March 17th, 2013. Open Database Camp will be held there. Sponsors are needed, make sure to specify you …

[Read more]
New feature: Microseconds in DATE/TIME values

MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

New feature: Microseconds in DATE/TIME values


MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

New feature: Microseconds in DATE/TIME values

MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

Showing entries 15993 to 16002 of 44964
« 10 Newer Entries | 10 Older Entries »