Skip navigation.

exploreopera

| Help

Sign up | Help

Opera community blog

fred

Behind the scenes at the Opera community

Bringing back the news...

Posted by cstrep · Tags: ,

Lots of stuff today :smile:

Anyway, I don't know if you already noticed. Some of you might, probably. The RSS feeds in your links section is probably already working again.
Not that they didn't work really, but let's say that they have been improved. Or rather, the downloading and update of your RSS/Atom/Whatever feeds is a bit more reliable now. There's still some problems, but for sure I know my feeds never worked and now they do! For a bit less boring feeds, go look at these or these, or you can suggest some or your own.

So, yes, you can use MyOpera as a feed-reader!
Not really wonderful, but... it should work now. Maybe you will have to wait 2-3 days for our feed spider to catch up...

10 comments

And the winner is...

Posted by cstrep · Tags: ,

As we said yesterday, we found out the reason the site was so slow last weekend, and some parts of Monday.
And the reason was that we got kindly hammered by some proxy servers that seem to be located in Vietnam,
requesting lots of "fake", as in "non existing" pages, always referring to the same user (that was already banned, don't know when).

These strange requests were referred to this user's blog, but they were totally fake, containing unusually long paths and as far as we know, they always resulted in the "banned user" page (or timeouts/proxy errors).

When we found this, we just temporarily disallowed requests having that strange pattern, and, voila', everything was working again.
They could be denial of service attacks (?), or just fake traffic thrown at us for some reason... who knows?

Anyway, we're at work now to implement a "throttling" mechanism, that will hopefully help stopping these strange guys from harming the site while improving overall stability of MyOpera. We're growing up... :smile:

11 comments

MyOpera outage

Posted by cstrep

EspenAO had just said that we managed to reduce our downtime, and Boom! Community's down.
Our main database master server just crashed badly. Investigations are underway.

The brave Nicomen and I just finished restoring the services back online.
There are still some glitches here and there, but things are steadily coming back to defcon 5.

Oh, and please say 'goodbye' to these lovely "Proxy Errors" because we're going to replace that message with something more comprehensible to human beings. However, our goal, of course, is to not have them at all :-)

92 comments

Pharmacy and nurse schools blog spammers

Posted by cstrep · Tags: , ,

Lately we have been targeted by some bad spammers that fill their "wonderful" blogs with hundreds of posts about pharmacy, nurse schools and other crappy stuff. They probably use semi-automated tools, and for several reasons, this drains server and database power for "the good guys".
This is the reason for so many proxy errors and site slowdown...

But don't despair! We have just sent live an optimization regarding new blog posts that should hopefully help the database a bit when these spammers hammer us.

We're also working to some sort of throttling that should slowdown people from posting in their blogs if the frequency of post is like 1000/minute or something :-)

I think no legit user, apart maybe from Tamil, is able to do that... :-)

15 comments

OpenID on MyOpera?

Posted by cstrep · Tags:

If there's enough "demand"... :whistle:

32 comments

Regular bug fixing in progress...

Posted by cstrep · Tags: , , , ...

Hi to all "devblog" friends,

after some time spent on backend optimization, stress testing, and lately on a new file storage architecture (seen the new avatar paths?) and on MyOpera internationalization support, yes, that's a lot of stuff, I'm back to regular bug fixing.

There are lots of open bugs, some of them have been there for a loooong time. We know, but we had some structural problems and various urgencies that called for immediate action. Anyway... I started friday on this "intensive" :smile: bug fixing, and seems I already managed to fix a few long standing, annoying bugs:

  • #1719: When saving events(countdowns) in a group you get redirected back to your personal page.
  • #1650: Use less compression on JPEG user pictures. Now JPEG images are saved with quality setting to 95, which should be pretty good, and also, no more ugly black borders. Now images are scaled and automatically cropped. :-)
  • #1970: Sometimes a blog RSS feed was displayed differenly whether the URL ended with '/' or not.
  • #1783: User privacy settings are not saved properly. This means that in your personal account page, if you chose to show your login status only to 'Friends', it didn't save the preference correctly. Now it does.
  • Other random tickets, mostly not relevant for users.

All of this is now fixed in the development version of MyOpera. Will go out with the regularly scheduled release cycle. Thanks for listening and stay tuned.

17 comments

Stress testing tools for MyOpera

Posted by cstrep · Tags: , , ,

Here at MyOpera we are currently researching on some stress testing applications. Basically, we want to be able to:

  • evaluate the impact of performance-related code changes simulating real production load
  • have a "cache warm up" procedure

Tools of the trade

There are many stress testing applications out there. We are still looking for alternatives, but so far these seems roughly what we need:

  • httperf - a simple HTTP threaded performance measuring application written by HP research labs
  • siege - multithreaded stress testing load generator, flexible and simple to use
  • jmeter - a Java desktop application that can visually define workload for stress testing, lots of possibilities. Can also analyze web server logs and replicate production load. IMHO, the interface sucks badly.

There's also another common tool for database-only stress testing, super-smack. Probably we will use this for db queries optimization and benchmarking.

Progress so far...

Siege has been the simplest and quickest to set up and use. We already built some custom workload profiles for MyOpera, to test cache contention with production-like load and to warm up our cache/backend servers after application upgrades. It could also be used as a simple functional test tool, for instance to verify that a list of urls are working correctly. But we already have that, and Jmeter is much better for that purpose.

BTW, if there's anyone with JMeter experience, please speak up! I'd love to hear from you... :-)

5 comments

get your own blog at my.opera.com
August 2008
SMTWTFS
July 2008September 2008
12
3456789
10111213141516
17181920212223
24252627282930