- Recent
- Popular
- Tags (1)
- Subscribers (23)
- MySQL University for up to 100 attendeesToday
-
Yesterday (December 4th), Sergey Petrunia gave a presentation on what's new in MySQL Optimizer. Unfortunately, the slides didn't show up in the Dimdim presentation area, which also means that the recorded session only has Sergey's voice but not the slides. (I've filed a bug in Dimdim's issue tracker.) However, Sergey kept referring to slide numbers in his talk, so it should be fairly easy (just not as convenient as usual) to follow his recorded presentation.The slides, together with links to the recording and the chat transcript, can be found on the MySQL University session page.
Next week (Thursday, December 11th), we'll use our brand new commercial Dimdim license to run the session. This includes a new session address / Dimdim URL:
http://webmeeting.dimdim.com/portal/JoinForm.action?confKey=mysqluniversity
You can bookmark this one; it will remain valid for all future sessions. Reme
- MONyog 2.9 Has Been releasedToday
-
Changes (as compared to 2.83) includes:
Features:
* This release adds a ‘base time’ setting in MONyog. This setting (if defined by user) will be used for calculation of uptime-based counters. The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, the server status variables will be reset to the same value as would be after a server restart. There is one important exception however and that is the ‘uptime’ status variable itself. This single status variable is not affected by FLUSH STATUS. So to get true uptime-based counters in MONyog with servers that do not support the ‘uptime_since_flush_status’ variable (and currently only 5.0 COMMUNITY servers from 5.0.37 do - not ENTERPRISE servers and not any other major branch than 5.0 and also not 5.0 before 5.0.37) you will need to define a ‘base time’ in MONyog greater than or equal to the time where FLUSH STATUS was executed last time. Also you can now discard data older than a specific time by using this setting. Refer to documentation for full details.
* Improved the purging logic with the MONyog embedded database. Now also system CPU load is considered and purging operations will be skipped if CPU is high. This is a further improvement to the change in purging logic introduced in version 2.5.
As compared to 2.9 Beta1 this also includes:
Features:
* MONyog can now be running behind an Apache server configured as ‘reverse proxy’.
- Destroying MySQLYesterday
-
Let’s say we wanted to destroy MySQL. Basically, make sure no one EVER uses it again.
Further, we want to simultaneously con as many people to fall into the MySQL trap and release products only to have MySQL crash and dump core. (This would have the added benefit of completely destroying the MySQL brand as new developers complain how they migrated to MySQL 5.0 only to have it crash.)
Well, I would perform the following:
- Release MySQL 4.1 with crash bugs. Further, release features like subqueries that are pathologically designed to not actually use any indexes.
- When the community complains, promise to never do it again and that you’ve learned your lesson. Spend the next 6-12 months fixing these bugs.
- Release MySQL 5.0 with crash bugs. Basically, cram as many features as possible and only begrudgingly accept patches.
- When the community complains, promise to never do it again and that you’ve learned your lesson. Spend the next 6-12 months fixing these bugs.
- Further, release TWO versions of MySQL and screw over your original community by keeping the latest and greatest releases from them. Also, screw over your new community by making sure the new releases aren’t tested.
- Spend years talking about the quality of the next release and the massive new (and awesome) feature set.
- Amazon SimpleDB Grows UpYesterday
-
A nice blog from the AWS team describing what's new with SimpleDB now that it's going into public beta.
Some things to note:SimpleDB makes it easy to scale. You don't have to worry about creating a complex master-slave setup to support a high level of concurrent access. In fact, concurrent access is where the SimpleDB model really shines. Fire up a bunch of threads and start sending requests our way. SimpleDB can handle the load. In fact, during the private beta the developers at Pluribo scaled their application up until it was making 5600 requests per second
- 60 day free trial for up to 1GB of data
- 30 day free trial of the Simple DB Explorer, including upload of MySQL data into SimpleDB
- Tools for various languages, including Java, Python, Ruby, and ActiveRecord
- Queries can include sorting on any attribute
- Coming soon: a SELECT-like API and batch loading
http://aws.typepad.com/aws/2008/11/amazon-simpledb-grows-up.html
- MySQL Query Analyzer -- A tool to pinpoint slow SQL code in MySQLYesterday
-
Recently, MySQL introduced the MySQL Query Analyzer tool, which can help DBAs resolve performance problems in their SQL code. The tool monitors query performance and shows SQL code that is causing a slow down without relying on the slow query log. DBAs can take this information and use it to further tune their environment to achieve better performance. You can watch a small demo here to see the product. Note that the Query Analyzer tool is available with MySQL Enterprise. A trial version of MySQL Enterprise can be downloaded for 30 days at http://www.mysql.com/trials/.