Read Partitioning In MySQL, Part 1 before reading
this post.
Partition pruning is the most critical
performance component about partitioning. Partitioning can ease
management of your data (for example the ability to just backup
or restore a single partition or the ability to drop a no longer
needed partition) but the main reason people add partitions is
for performance.
Pruning helps performance by only reading the partitions that
need to be read for a query. For example, if you have a table
range partitioned by year that has partitions for the years 2000
through 2010. If you write a query selecting data between 2002
and 2005, you don't want to have to scan all 10 partitions.
…
The support for Rails in NetBeans IDE has improved considerably in the past few days. Greg and Ludo have been working on ramping up the jMaki NetBeans module as well. This screencast is an update to #web2 and shows how the development experience for creating a jMaki-enabled Rails application is drastically simplified.
The screencast shows how a jMaki-wrapped Yahoo and …
[Read more]
I talked about this matter already, but now it's
time to wrap up.
The Summer of code is over, and the project I have mentored is
finished, with a new tool as its outcome, the MySQL test creator.
The student who developed this tool, Charlie
Cahoon, did a decent job. All in all, considering that it was
his first serious developing experience, he got an excellent
result. The maturity stage is still alpha, but he did the
breakthrough work to get the development of this tool in the
right track.
What do we have in hour hands? A tool that will speed up and make …
The glut of information was dulling awareness, not aiding it
--Jerry Mander
The aggregate tables enhance reporting performance1 by reducing
the amount of data that needs to be queried for widely used
reports. Aggregate awareness at the database or the query tool
makes the use of aggregate tables transparent to the user of the
data warehouse.
Consider the example star schema for a financial services company as a
simple case for aggregations:
|
Account (customer) 30 million records |
|
|
|
Product |
|
|
\ |
|
/ … |
I’m looking for 2 PHP Programmer for the company I’m working for. I’ll be hiring a Senior and Intermediate PHP programmer. If you’re in Montreal, QC and intrested in drop a comment I’ll contact you. This is not a webmaster/designer etc job, if you’re a pure PHP programmer I want you! Position: Full Time, Permanent Industry: IT Multimedia/Entertainment Qualifications: PHP, MySQL, [...]
This release is part of the unstable 1.5 branch. Its features will ultimately go into the stable 1.6 branch. You can download it from the innotop-devel package.
The major change is a new Command Summary' mode (switch to this mode with the 'C' key) that's similar to mytop's 'c' mode. It shows you the relative size of variables from SHOW STATUS and SHOW VARIABLES.
As I mentioned in the Post Scriptum of an earlier post, JavaScript is not the only language that you can create CouchDB views with. You can now use PHP, too.
Here is how views work again: You specify a JavaScript function that receives a document parameter (which is a JSON object). You can do whatever to that object and return it again. Or you don’t return anything. When a new document is added to a CouchDB database, it gets passed to the JavaScript function and, depending on its return value, is included into the view that is associated with the function &endash; or not.
function(doc)
{
if("Value" == doc.field) {
return doc;
}
}
This function adds the full document to the view when it has a
field called field and when that has the value
Value. This is just a refresher on how views work …
I hope I got your attention with the title. The politically
correct term should be "how to redirect MySQL traffic on Linux",
but you probably wouldn't have noticed.
The scenario is this. You want to switch servers without need for
the clients to change connection parameters.
Why would you want to do this? Some reasons:
- You want to test a new server version, which you installed to listen to port 13306, and you want to do it without modifying the applications parameters;
- You ant to use MySQL Proxy on port 4040 to log the traffic for a while without restarting the server, in order to debug an inexplicable problem;
Whatever the reason, you can do it.
Here is how you can proceed on Linux.
Set a iptables rule to redirect port 3306 to port 13306 or to
port 4040:
sudo …[Read more]
MySQL AB is a global company. The employees are spread around the globe. It is impressive to see that this works for a technology company, where high-bandwidth communication between its main players is crucial to their success.
Once in a while though, they need to meet in person. This year, all developers meet in Heidelberg, Germany for a week. They will have workshops, training and lots of get-togethers.
MySQL AB even invited a few community members to take part in the event for two days. I managed to sneak in there and I am looking forward to see a lot of the people I met in Santa Clara earlier this year and those I have not met, yet, but read a lot online. To top it all, Damien is there. Guess what we are going to talk about.
I promised to blog my hands off in exchange for the invitation, so expect some coverage …
[Read more]
I finally got my visa so I'm going to MySQL Developers meeting in
Heidelberg, Germany next week.
Hopefully it will be great source of "technical insight"
information, either from organized sessions or from developers
themselves.
Plus I'm looking forward meeting a lot of friends our where both MySQL Developers and active community members.
Entry posted by peter | 2 comments
[Read more]