Posts Categorized: MySQL
I was asked this question in an e-mail — feel free to ask your questions in the comments, as I will point the original author to this post to answer those questions. There is not a lot of data here, so instead of me asking questions in an e-mail I figured I would open it up to the (MySQL) world. Without further ado, here’s the question…
We’ve been running into a problem with one client: SELECT COUNT(*) FROM tbl; takes 0.25 seconds on one db, and 0.06 seconds on another.
Consistently. That’s a fourfold difference. There aren’t any significant configuration differences (like query cache, etc.), the software versions are the same, and the table fits into memory. This has been looked at by at least 3 in-house MySQL experts, and the only thing we can determine is that it’s a hardware difference.
I have created a MySQL Professionals Group for networking with others in the space, in the tradition of the Oracle Professionals group and the SQL Server Professionals groups that I already participate in. This is a great way to network with other professionals in your field of work. I hope you join us.
Are you interested in attending the 2008 MySQL Conference & Expo? I’m happy to announce that LinuxQuestions.org is able to give away one pass to the event. Visit this link for additional information. Good luck.
Here is the video of “Database Basics”, which I presented at the February 2008 Boston MySQL User Group meeting. The presentation goes over the basics of relations, data, the Entity-Relationship Model, how to choose data types, and how to do basic CREATE statements.
If you have a 12-server MySQL Cluster with, 1 Management Node, 3 SQL Nodes, 2 Data Node Groups, and 4 Data Nodes per group. And each machine is configured to allocate 1G of memory for its function, how much data (data + indexes) can you store in total in your cluster?
Welcome to the 88th edition of Log Buffer, the weekly review of database blogs.
I have been automating to make the life of my team members easier. As part of the DBA service, we offer monitoring in the form of alerting, and also in the form of daily checks to ensure everything is running smoothly. Daily checks consist of things that do not need to be checked every minute, but should be checked frequently. This is very valuable to ensure that no changes get lost. A DBA might be adjusting the configuration, but forget to put the final changes in the config file. In that case, the next day our daily checks will throw a warning, and that DBA will say “oh yeah, I forgot to put that into the config file!”
Open Source means that the source code is open. There are many inferences that can be made from this, and many stereotypes that can be applied, but in the end, all it means is that you can read the source code as well as use the binaries. One of my team’s current tasks is to restore a backup (using InnoDB Hot Backup, and compressed) from a client’s production machine to a development instance…weekly — thus we want to automate it. We got everything going well, except uncompressing the production backup and applying any logs (with ibbackup).
I was recently asked a question by someone who had attended my Shmoocon talk entitled “Why are Databases So Hard to Secure?”. (PDF slides are available). I was going to put this into a more formal structure, but the conversational nature works really well. I would love to see comments reflecting others’ thoughts.
Recent Comments