Sun has launched the Glassfish Portfolio, the best web application platform on the planet.
To learn more, you can also go to "the Aquarium" and "Miles to go...."
Sun has launched the Glassfish Portfolio, the best web application platform on the planet.
To learn more, you can also go to "the Aquarium" and "Miles to go...."
Sun has launched the Glassfish Portfolio, the best web application platform on the planet.
To learn more, you can also go to "the Aquarium" and "Miles to go...."
Yesterday Sun introduced Glassfish Portfolio. Its a new stack of open source middleware products including Glassfish Enterprise Server, Glassfish ESB, Glassfish Web Space Server, and the new Glassfish Web Stack, which includes support for projects such as Tomcat, Memcached, Apache, PHP, Ruby and Python and a copy of MySQL Community.
It’s a pretty complete infrastructure stack. What it is not, however, is an integrated LAMP stack, despite Sun’s reference to it as such not once but twice on its press announcement.
Glassfish Portfolio runs on Linux of course, as well as Solaris, but it does not contain Linux (integrated or otherwise) or Linux services (although that is available …
[Read more]
At a customer yesterday, I confirmed what Jonas
suspected and what is probably related to bug 42474. Scroll down and look for the output of
SHOW PROCESSLIST.
It seems that TRIGGERs causes Table Locks to be
taken when used with Ndb cluster tables!! I have created a
bug report .
If we do an update on a table that has an update trigger the
trigger will upon execution lock the entire table that is
affected by the trigger.
This was verified by having several threads updating random
records in a table. When one update gets to execute, the trigger
will block the other updates from happening. This was shown using
SHOW FULL PROCESSLIST¸ which shows a bunch of
statements being in …
This was an interview Jack Adams did with me at the MySQL/OpenSolaris booth at FOSDEM last weekend. Jack adams is an OpenSolaris mascotte, look around on YouTube for more funny interviews with him.
So i finally defeated my 'inner Schweinehund' and set up a working Windows development system again. Using the Visual Studio C++ 2008 Express edition i'm now able to compile UDF projects generated by CodeGen_MySQL_UDF aka. udf-gen, and the udf-gen script now works natively on Windows, too.
Continue reading "MySQL UDF generator finally
supporting windows"
An often overlooked and way underrated component to any site is the collection and reporting of solid historical performance metrics. Don’t get me wrong, everyone collects some sort of web page stats, has access to mysql status variables, and uses top to check cpu and process stats ( what else does anyone need right?). But the metrics I am talking about are not your simple # of pages,# of users, apache log metrics that everyone has in their web server, nor are they point in time cpu stats, or cumulative row accessed counters. No, we are talking about true performance stats, gathered over a long period of time. These stats can be used for troubleshooting, trending, and make great art and conversation pieces ( have seen my one of a kind CPU graph).
Think of it this way, someone complains your site is slow. They say when they hit the first page it just seems sluggish. What does …
[Read more]This is one of the largest issues so far. In addition, it has some of the best content we have ever had. The articles are all in-depth with some exciting new information:
It is available for download, along with all …
[Read more]After a discussion with Adam Dixon over ways to retrieve binlogs from remote servers we came to the conclusion that mysqlbinlog should have a way to retrieve binlogs direct from a remote mysql server and save them in raw binlog format.
So after a little bit of tinkering I came up with a small prototype patch to do this, to use this simply do:
mysqlbinlog --raw --result-file=out.bin -t -R --host=192.168.1.101 mysqld-bin.000001
This can probably be extended to wait for more data rather than ending when it hits the end of the log, but this is just a proof of concept for now.
This new patch against MySQL 5.1.31 can be found here.
I've been following the info from Kaj's info/feedback session at
FOSDEM. I was going to write my thoughts as a comment, but I
think it can benefit from being a post by itself.
What strikes me is that the items raised and "voted on by hand"
are all existing and actually long-standing issues., most even
pre-date MySQL's acquisition by Sun. Given this, why would
raising the same issues once more have a different result this
time? Doing the same thing again tends to yield similar results,
but changing other parameters may change the outcome. Which
parameters, specifically, are to be changed?
The good intentions of those involved are not in question.
However, it just doesn't appear to deliver. Announcements are not
cool. Ongoing statements "we want a shorter release cycle"...
sorry guys, that's old news; I fully trust …