Mercury 0.9-Beta released

Events happening in the community are now at Drupal community events on www.drupal.org.
Greg Coit's picture

Mercury 0.9-Beta has been released. Updates in this version include:

1) mysql configured to use per-table storage for innodb
2) apc replace by memcached (apc is still installed and can be enabled in settings.php)
3) mecached configured with 8 bin by default

And as mentioned before, we're starting support for BCFG2 server configuration. BCFG2 will be fully supported by the next (1.0) release of Mercury.

The AMI names are PANTHEON-pressflow-mercury-32-0.9-Beta.manifest.xml and PANTHEON-pressflow-mercury-64-0.9-Beta.manifest.xml

AMI ID's are:

us-west:
32: ami-c7530282
64: ami-c1530284

us-east:
32: ami-e146ab88
64: ami-e346ab8a

eu-west:
32: ami-93c6ede7
64: ami-81c6edf5

As always, please post questions to this forum and bug reports to https://bugs.launchpad.net/projectmercury. We'll update the instructions at http://groups.drupal.org/pantheon/mercurywiki with 0.9 in the next few days.

Comments

Woohoo!

Macronomicus's picture

I cant wait to test this out!

Does Memcached completely replace all functionalities of APC including Opcode cache? Or should we use both in tandem? The big difference I see is that memcached can do distributed caching. Ive never tried memcached .. this should be quite interesting to dig around in.

Cheers!

No, memcache has nothing to

Alexander Langer's picture

No, memcache has nothing to do with PHP, so you better go with APC as opcode cache and memcache as data cache to benefit from both.

Thats what I was thinking, I

Macronomicus's picture

Thats what I was thinking, I read a few things around the net which pretty much said just that. It will be interesting to see how memcached compares to APC on the data caching, especially with all that multi-bin stuff.

To clarify, the switch was

msonnabaum's picture

To clarify, the switch was from the cacherouter module using APC for the cache tables, to the memcache module.

APC is still being used for opcode cache.

One advantage that Memcache has over APC for cache tables is that you can distribute the memcache bins over multiple machines, or another machine altogether. APC's cache is per node, so its not as flexible in a clustered environment. Also, the memcache module supports sessions (which mercury is not using btw), whereas the cacherouter module still does not.

You can always check out the confs on launchpad for more details:

http://bazaar.launchpad.net/~gregcoit/projectmercury/trunk/files/head%3A...

Be great to hear if you get

SeanBannister's picture

Be great to hear if you get APC and Memcache running together I tried to do this a few months ago but with my lack experience in the area I didn't have much luck. I believe cacherouter is working on support for multiple caches but when I looked it wasn't complete.

I was also wondering why the

dalin's picture

I was also wondering why the switch from APC as NoSQL cache to Memcache.

--


Dave Hansen-Lange
Director of Technical Strategy, Advomatic.com
Pronouns: he/him/his

CacheFlow

joshk's picture

While I love the power of cacherouter, Pressflow is going to internally add a system called CacheFlow that will provide an even more optimal L1 cache in APC:

https://blueprints.edge.launchpad.net/pressflow/+spec/cacheflow

Looking at a 1.0 release soon, I want to be ready to take advantage of that, and it will conflict with using cacherouter+apc, so hence the change.

Havent tried the EC2 image

bennos's picture

Havent tried the EC2 image yet.

Looked at launchpad and the wiki article.
why did you not use MySQL 5.1 ?

I have installed Mysql 5.1 on some server and it is stable enough.
there is an improved MySQL Version from Percona with a better InnoDB Plugin.
At http://www.mysqlperformanceblog.com/ you can find a lot of performance test.

Installation of Percona MySQL version is simple. just adding the repos to the sources.list
deb http://repo.percona.com/apt jaunty main
deb-src http://repo.percona.com/apt jaunty main

Thanks!

Greg Coit's picture

bennos,

Thanks for the links. We'll take a look at these for 1.0.

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

Sticking with Ubuntu Repos for now

Greg Coit's picture

Bennos,

For the moment, we're going to stick with the Ubuntu Repos for Mercury for stability sake. Hopefully, MySQL 5.1 will be included with Ubuntu Lucid (and/or backported to Karmic).

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

Why are there 2 defaults in

ManyNancy's picture

Why are there 2 defaults in the memcache config?

                  '127.0.0.1:11211' => 'default',
             '127.0.0.1:11212' => 'block',
               '127.0.0.1:11213' => 'filter',
              '127.0.0.1:11214' => 'form',
            '127.0.0.1:11215' => 'menu',
            '127.0.0.1:11216' => 'page',
            '127.0.0.1:11217' => 'updates',
             '127.0.0.1:11218' => 'default',

Is this necessary/correct? Thanks.

Neither...

Greg Coit's picture

ManyNancy,

Neither necessary or correct. The last should be either cache_content or cache_views. We'll make sure this is fixed in the next release (1.0).

Thank you!

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

So we should replace the two

Macronomicus's picture

So we should replace the two default lines with cache_content and cache_views?

The best solution

Greg Coit's picture

The best solution is 9 bins:

'127.0.0.1:11211' => 'default',
'127.0.0.1:11212' => 'block',
'127.0.0.1:11213' => 'filter',
'127.0.0.1:11214' => 'form',
'127.0.0.1:11215' => 'menu',
'127.0.0.1:11216' => 'page',
'127.0.0.1:11217' => 'updates',
'127.0.0.1:11218' => 'views',
'127.0.0.1:11218' => 'content',

This change will be included on Mercury 1.0

Hope this helps,

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

ok so have a default too,

Macronomicus's picture

ok so have a default too, thanks Greg .. im leaving memcached out of use while I dev my site but it seems pretty cool. I tested and played with it a bit & I do like it more than the cachrouter option.
Cheers!
Joshua

'127.0.0.1:11218' =>

Flying Drupalist's picture

'127.0.0.1:11218' => 'views',
'127.0.0.1:11218' => 'content',

Is views and content supposed to be in the same one?

typo

Greg Coit's picture

Flying,

Nope, that's a typo. Should be:

'127.0.0.1:11218' => 'views',
'127.0.0.1:11219' => 'content',

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

AMI available in EU?

james_agnew's picture

As per your post, I searched for the new AMIs in EU-WEST:

32: ami-93c6ede7
64: ami-81c6edf5

but all that comes back is 0.81

ami-671d3613: chapter3-storage-europe/PANTHEON-pressflow-mercury32-0.81-Beta.manifest.xml
ami-371d3643: chapter3-storage-europe/PANTHEON-pressflow-mercury64-0.81-Beta.manifest.xml

Would you mind checking that the 0.9 AMIs are indeed available in EU please?

Thanks, James

Fixed

Greg Coit's picture

James,

Thanks for the heads up - the images we're still private - this has been fixed.

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

I just read some

SeanBannister's picture

I just read some documentation and listened to a podcast about BCFG2 and I'm more confused than when I started :| I'm looking forward to the documentation update on this.

Agreed

Greg Coit's picture

Sean,

BCFG2 can be intimidating at first. After playing with it the last few weeks, I'm sold on it's power and flexibility. We'll have a section of the wiki devoted to using bcfg2 soon and it should make much more sense.

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

Sounds great!

BenK's picture

I've been following the Project Mercury development for awhile now and it looks like it has been really fleshed out... looking forward to trying this out!

Thanks,
Ben

High performance

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: