I've been running a series of sysbench tests on Innodb with MySQL
4.1 My tests include doing both reads and writes on the
table.
I've noticed that after the test is complete, and while there are
no processes in show processlist, I see a fairly large amount of
buffer pool reads and writes, as well as a large number of
Modified db pages. Now, I know that it could take a while for
innodb to flush out the dirty buffers after a large amount of
writes, but I'm seeing the Modified db pages actually getting
larger for a while, and then gradually getting to the point where
it finally settles down and returns to 0.
The only thing I can think of is Innodb is doing some sort of
table optimization, which begs the question of whether I should
rerun my tests with the optimized table or not.
Has anyone else seen this?
UPDATE: I believe I have figured out what's happening. My
sysbench test is working on a …
Si Chen wrote recently about the growth limits of open-source projects. He points out that as a project becomes larger, it gets harder to maintain. I can only agree. As the MySQL Toolkit project has grown, it's become significantly more work to maintain, document, and enhance.
We have fixed the issue with the PHP dtrace extension not working in Cool Stack 1.2. As I mentioned in my announcement post, we had already identified the issue but didn't have time to fix it before the release. The issue was that /usr/ccs/bin/ld was being used to do the linking but this doesn't work for dtrace as some initialization code needs to be called from the .init section and this is not setup correctly if we don't use 'cc' to do the linking (rather than 'ld').
So a simple addition to the configure line:
LD="cc"
did the trick.
We now have two files : dtrace_1.2_sparc.so and dtrace_1.2_x86.so posted. Download the one for …
[Read more]We have fixed the issue with the PHP dtrace extension not working in Cool Stack 1.2. As I mentioned in my announcement post, we had already identified the issue but didn't have time to fix it before the release. The issue was that /usr/ccs/bin/ld was being used to do the linking but this doesn't work for dtrace as some initialization code needs to be called from the .init section and this is not setup correctly if we don't use 'cc' to do the linking (rather than 'ld').
So a simple addition to the configure line:
LD="cc"
did the trick.
We now have two files : dtrace_1.2_sparc.so and dtrace_1.2_x86.so posted. Download the one for …
[Read more]
(Please watch this youtube video to fully appreciate the "the future
is today" joke)
What are federated tables?
The FEDERATED storage engine is available beginning
with MySQL 5.0.3. It is a storage engine that accesses data in
tables of remote databases rather than in local tables.
(the link to the mysql site)So federated tables are
tables that lookup data from regular tables that are on remote
server, meaning somewhere else over your network or internet.
This is very interesting to me, because it technically saves you
a lot of coding to update your tables manually from another
server.
Here is an article from O'Reilly - …
One of the enhancements I added to MySQL Archiver in the recent release was listed innocently in the changelog as "Destination plugins can now rewrite the INSERT statement." Not very exciting or informative, huh? Keep reading.
A
So I was wondering.... sometimes you dont know if you need to
define your search a little more by adding another column and
another variable.
What do I mean? I mean this:
select * from table where something = 1
so the 'something = 1' part defines the search.
BUT, what if you sometimes need to use 'something = 1' and
sometimes you would just like it to search everything?
Doing it in the application layer/logic
Well, basically, what I used to do is play around with it in my
application. For example:
$sqlstr = 'select * from table';
if ($something > 0 ){
$sqlstr = ' where something = 1';
}
As you can see, I first made the generic search. In case that I
need to define it further, I simply add to the existing string
with the search criteria.
But I always wondered, how can you just do it directly in the SQL
statement.. …
This release fixes some minor bugs. It also adds a few major new features to several of the tools. The command-line option and help functionality, as well as several other pieces of common functionality, has been replaced with common modules that have a test suite. This is the first step towards a gradual rewrite to replace untested 'script' code with tested, maintainable code.
Si Chen wrote recently about the growth limits of open-source projects. He points out that as a project becomes larger, it gets harder to maintain. I can only agree. As the MySQL Toolkit project has grown, it’s become significantly more work to maintain, document, and enhance. (This is why I’m asking you to sponsor me for a week off my regular job to work on MySQL Table Sync, by the way.