Skip navigation.

My Opera News

Behind the scenes at My Opera

My Opera now running on a master to master replication setup

, , , , , ,

The scheduled database maintenance was completed on Saturday. Well, it wasn't exactly maintenance, but rather an important change of setup. Now My Opera is running on a master to master replication setup, instead of the classic master-slave that has been running for some years now.

There's at least 2 good reasons why we chose that setup:
  • it allows for database master maintenance with practically no downtime, since you can have the site run on your secondary master, while the primary is taken offline. When maintenance is over, you can switch back to the primary.
  • in case of disaster or failures to the primary master, the secondary can kick in (manually for now) in a rather short time. Last time we had a primary master db crash, it took us something around 4-6 hours to be back online.


So, currently My Opera is running on the secondary master database, while the primary is being prepared. "Being prepared" in this case means that we're converting some of our heavy duty tables to the InnoDB storage engine. This was really needed because MyISAM table-level locking poses some hard limits on concurrency and scalability of your database, even if it's very fast. Add that we have more user activity, APIs and services than ever before, and you have the whole picture.

Of course, all this work should also improve raw performance of the site. Once we get back to our primary master server, which we will probably do in the next few days, the site will be definitely faster. Not ludicrous speed yet, but faster :smile:

Scheduled downtime for database maintainanceBack to our primary master database

Comments

David Tsunamy 16. November 2009, 21:36

Yaaaah!!! :D Thanks!!!! :yes:

Robert Jacobsen 16. November 2009, 21:37

Need more lolcats!

Rafael Luik 16. November 2009, 21:40

Originally posted by cstrep:

database master maintenance with practically no downtime

:yes:

Tamil 16. November 2009, 22:43

Шуйский Николай [krigstask, Ŝtérkrìg] 16. November 2009, 22:47

we're converting some of our heavy duty tables to the InnoDB storage engine. This was really needed because MyISAM table-level locking poses some hard limits on concurrency and scalability of your database


That's MySQL for you (-;E
Why not PostgreSQL?

Daniel James Hendrycks 16. November 2009, 23:25

:up:

Muttsfan 16. November 2009, 23:29

Stand by for ludicrous speed




LUDICROUS SPEED! *GO!*



AAAAAAAAAAAAAHHHHHHH, MY BRAINS ARE GOING INTO MY FEET!!!

selurus 17. November 2009, 04:56

:up:

Charles Schloss 17. November 2009, 13:43

Mick-E 17. November 2009, 22:52

:wait: ing 'til we go to plaid.

53north 19. November 2009, 00:39

Opera still shows 50kb a page load, the platform I'm moving to averages 8kb -
somewhat better for low order mini browsers and has paid professional mods.
It allows mature topix too without some jealous trolls coming by and flagging stuff to achieve take downs off their percieved rivals - from the gullible naive busy part time 'moderator'.

Purdi 19. November 2009, 12:38

WTF is 53north talking about?

Daniel James Hendrycks 19. November 2009, 22:31

Originally posted by Purdi:

WTF is 53north talking about?


Please change your tone. :troll: http://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Sockcat.jpg/582px-Sockcat.jpg *sockpuppet*

David 20. November 2009, 23:08

hmm... okay then...

WTH is he talking about?
(Hell is okay, isn't it?)

I think 53north talks about blogspot (at least that's where his blog seems to move to). I just don't know where he got his statistics from, but can't be his own site: His "heavy load" MyOpera blog has a load of 10.3kB, while his "slender" blogspot site has a load of 16.4kB. :rolleyes:


This means that in theory with UMTS (without HSDPA) his MyOpera blog would take 0.21seconds to load, while the blogspot blog would need 0.34seconds. The blink of an eye takes around 0.3-0.4seconds... just mentioned for comparing reasons.

53north 21. November 2009, 04:15

I'm seeing 163Kb for this page.
About 30Kb now for one of my blog posts. - on operamini, that's the difference between load and no load. Even the top bar here is a 21Kb png when <#cc0000 > would do it for nothing..
Besides, what's the point in putting stuff up (found on a safe search on google) if someone comes along and maliciously flags it.
The opera team react with a take down policy at the first flag - despite 3 of the albums being top hit for 6 months.

David 21. November 2009, 11:58

Well it's up to you to change the style of your blog. You can rewrite most of it within a few minutes. So that's not really an argument.
Concerning the policy for illegal or copyrighted content I must admit that I haven't had any trouble so far, but I'm pretty sure that the opera team takes a look on flagged content before removing it. But we wander from the subject.

53north 21. November 2009, 16:36

My blog text isn't a problem. And I can get to the custom design to lighten the header Kb. It's operas reliance on a mobile site option (which is still overly heavy) - when they speak of the operamini as a 'full browser experience'.
=o}
Start a small trial blog at Blogger and you would see an immediate difference on a phone, anyway.

selurus 21. November 2009, 19:20

I prefer to view websites in mobile view and I think that My Opera blogs render well in Opera Mini. The blogspot blogs dont render in the mobile view at all. I think Wordpress blogs render well in Opera Mini too.

Charles Schloss 21. November 2009, 19:36

It also depends on the content of the blog and how big in size that content is, people have different connection speeds also

Write a comment

You must be logged in to write a comment. If you're not a registered member, please sign up.