dist-git 应该会伴随 F14 的到来而到来的。cvs 系统就要说再见了。
---------- Forwarded message ----------
From: Jesse Keating <jkeating(a)redhat.com>
Date: Fri, Jun 11, 2010 at 5:44 AM
Subject: dist-git project update
It's been a while since I last updated folks on dist-git, and in reality
it's been a while since I last worked on it. Fedora 13 took up all my
Since my last update we've made great progress on fedpkg, the new tool
that will replace the make system. It is packaged up with
fedora-packager and has the ability to do many tasks that our Make
system handled. Here is a quick list:
Many of these targets take optional arguments which extend their
functionality and replace some other specific Make targets. This list
is enough to get us checking code out and in, and building in koji.
On the koji front we've recently discovered the changes necessary to
build from dist-git style repos, and those changes are being polished up
and committed upstream. We have done multiple builds successfully from
Where do we go from here?
We're ready for more wide scale testing, and to facilitate that I am
refreshing the git repos from current CVS (people with existing clones
will have to blow them away and re-clone), and getting a koji stage
instance up that we can build against (with limited builders). We'll
then push out another fedora-packager update that has the right URLs to
build against this stage Koji and announce that it is ready for
Based on this testing, and some decisions around git tagging and branch
usage, we stand a good chance at being able to roll this out prior to
the F14 branch event. I hope you are all as excited as I am about this!
Fedora -- Freedom² is a feature!
devel mailing list
Fedora && Debian User, former Ubuntu User
My Page: http://www.liangsuilong.info
Fedora Project Contributor -- Packager && Ambassador
If additionally you have to use different SMTP-servers depending on the
From-addr, then have a look at /Sendmail, too.
这篇文章介绍了 MySQL 5.1.47 里使用内建的 InnoDB 与 InnoDB 的插件之间的性
能差别。两者性能可谓天翻地覆。我一直以为 built-in 的话，应该会有更好的优
是在这个测试。是不是这个插件从 MySQL 5.5 中把 InnoDB 的特性 backport 出
刚好 Fedora 12/13 的源里都是 MySQL 5.1.47 这个版本，大家可以留意一下。
Sent to you by liangsuilong via Google Reader: Performance gain of
MySQL 5.1 InnoDB plugin via Planet MySQL by Giuseppe Maxia on 6/6/10
You know already that InnoDB in MySQL 5.5 has great improvements in
performance and scalability. You will have to wait a few months for
that, though, because MySQL 5.5 is not GA yet.
But if you need some extra performance in MySQL 5.1, you may want to
use the Innodb Plugin instead of the built-in one. As of version
5.1.47, the Innodb plugin is of GA quality, and it comes with a good
out-of-the-box improvement compared to the built-in engine.
To test my assumptions, I used one of my test Linux servers to perform
a sysbench on 5.0.91, 5.1.47 built-in and plugin, and 5.5.4. The MySQL
servers were all configured with
MySQL 4.1.47 was tested both as out-of-the-box, and with the plugin
# note: the following statements must go all in one line
The test was the same for all the servers. A simple sysbench both
read-only and read/write on a 1M records table.
What came out is that, by using the innodb plugin instead of the
built-in engine, you get roughly 15% more in read-only, and close to 8%
Note that 5.5. enhancements are more impressive in scalability tests
with more than 8 cores. In this server, I have just tested a simple
I did some more testing using "ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=X"
in the InnoDB table, where X changed from 4 to 16. But sysbench didn't
seem to play well with compression. For low values of KEY_BLOCK_SIZE,
you actually get a much worse result than the built-in engine. I have
yet to figure out how I would use this compressed InnoDB in practice.
PlanetMySQL Voting: Vote UP / Vote DOWN
Things you can do from here:
- Subscribe to Planet MySQL using Google Reader
- Get started using Google Reader to easily keep up with all your