Powered By JFBConnect

Latest Blogs

image
Spockholm Server Maintenance Insights by Eike
Loot Lady

While waiting for the database server to load the data, I decided to do a little tech talk and give you an inside glimpse of some of our systems.

To dig a bit into the history, the idea of shortlinking mafia wars urls came up in the the old times of gifting and gift-links.

In the times of Link-a-Nator, we all worked with these awful long links, and posting them on Facebook was a mess. Until we came up with an improved version that would use tinyurls as shortlinks.
image
This worked for a while, but we often ran into problems with limits on the creation of tiny.com-links. Switching to bit.ly helped a bit, but not everybody was willing to create an account there.
That is when we came up with the idea of our own shortlinking database. Sure, it would be great to have control over the links, to use our own systems and not be faced with limit. Those few links should not be hard to manage, we thought. We were so wrong.
image
We decided to setup a system called Yourls, that is an open source shortlinking system based on PHP an Mysql.
image
We installed it, tested it, ran it and it was great. We even added the filtering of urls as our own option, since it was not supported by the system. Then it went live.
image
And crashed.
image
The reason: 400k urls in 24 hours. Our server should be able to handle that. Ok, so we looked more deeply into the yourls-code and found a few things that decreased performance.

Indexes: The main database tables did not contain any indexes. How could that happen? Well, it looks like the Spockon.me service was the first Yourls implementation with that high load happening. So we updated the code and added a few indexes here and there and changed a few SQL-statements.
Duplicates: When inserting a link, the database was searched if it contained a similar link. Not needed for us, we turned that off.

Ready to go live again.

And a month later, crashed again.

image
This time, the locking was a problem. Every time a shortlink was resolved (read from database), no new link could be inserted (write to database). Solution: Switch to row-locking instead of table-locking. Unfortunately the standard database format (MyIsam) is not capable of that. So we switched the whole database to InnoDB. Since changing the database format would have taken hours, we decided to make a cut and start with a blank database.

In the next weeks we also tweaked performance on the apache and the database-configuration and came up with a pretty decent and good working configuration. We stuffed the server with more CPUs and more memory and increased hard drive space.

Of course the database was used for other stuff too. We added the golden toolbar stuff,

image

our support forum,
image
and not to forget the family rank database, which is regularily updated with the family statistics.
image
After almost exactly two years now, the database has grown huuuuge. And with huge, I mean really really big. We are talking about a total database-size of 170 GB, with almost 50 million shortlinks created. This is really awesome, but made the database a bit hard to manage.

Especially the "feature" of InnoDB to use one file for all databases was getting a problem for us. Meanwhile we had a file of around 170GB sitting on the harddrive which would not shrink, even if we deleted data from the tables.

image
We decided to do a cut and once again start from scratch, because recreating that huge database is almost impossible. So we changed Yourls to write all links also to a secondary table, to which we would switch later. We were planning to follow this guide to remove the huge file.

Now this was in december, and it took us a while to get the time and effort to do this complex operation without losing any data.

We tested it two times on a copy of the production machine, so we knew it would work and be fast.

Additionally we are planning to make a maintenance script that cleans the database from unused requests, like property begging older than a week or other stuff that expires.

image
This was our action plan for today:

- Remove all unused tables and databases from the system (necessary cleanup)
- Shutdown the apache at exactly 6pm CEST
- export all databases to a dumpfile
- drop all databases
- shutdown mysql
- delete the ibdata1 file
- start mysql
- load dump.

The last point should be ready in the next half hour, while I spent the time waiting with writing this article. I hope someone read it to the end, if you're interested in the stuff we do, feel free to ask us question :)

I want to thank everybody who likes our scripts, everybody who used the service, and of course all those that helps with their donations to keep our servers up and running! You rock!!!

Spock On!!

UPDATE:

Something went wrong and we lost a few links. We're working on recreating them...

Original author: Eike
Continue Reading...
0
nimo5
Finding NiMo: The Awe Lizzy Continuum
Loot Lady

Since the saga began, many have asked whatever became of Awe Lizzy [1]. Her Facebook account was banned and the suspected reason is abusing reporting which is quite the opposite of reporting abuse. For those who think they can breath easy now, think again. While Awe Lizzy can’t be here to spread the good  word, two of her disciples can. Nikkie Randlls and Monique Valdez were faithful followers of Awe Lizzy and have now emerged as leaders in the campaign to stop bullying (aka attacking anybody who appears on the fight list). Collectively this dynamic duo is referred to NiMo.
I couldn’t possibly explain the campaign as well as NiMo but I don’t need to. The mission statement below sums it up nicely.
nimo1
The antics are identical to those used by Lizzy in the first part of this saga. Anyone who ends up on a NiMo attackers list is in jeopardy of being reported. While we all can argue what are valid reasons to be or not to be attacked, most would agree that reporting accounts to Facebook in hopes they will be banned is crossing a line.
nimo2
While the BOYD Family and others are trying to negotiate for peace as they did with Awe Lizzy, it’s not really working. For those interested in more on this issue, visit the BPS Peace Talks page.
nimo4

Thanks to the BOYD Family and all the others members of the “Admins. working to safeguard our members accounts” group for documenting this situation.

Original author: Mafia
Continue Reading...
0
attackers
Shrinking "Your Attackers" List
Loot Lady

Many players are reporting that the “Your Attackers” list on the fight page is shrinking. Normally your 10 most recent attackers remain on this list until new ones replace them. Maybe Zynga is looking into the erroneous fight list and player update data that appears in our game [1]. That issues seems to only be getting worse. I’m not sure if the Your Attackers list was simply reset and players who haven’t had 10 attackers are noticing or if some players don’t have 10 anymore. I have a full house! This isn't because of the Spockholm Toolbar feature that removes iced players, it's something that just started happening tonight. The 2nd image is a list with only 3 attackers and one is iced. Please let us know in the comments what is happening with your list. Thanks to Nikša Tudor for posting the 1st screen shot below on our fan page and to those who sent me inbox messages about it.
image

Original author: Mafia
Continue Reading...
0

Hopper Version 3 was released today.  The old Hopper will be discontinued March 8th 2013.  You must upgrade as it will no longer function.

Here are some of the new fetures in Hopper 3:

  • Full Family Bucket Support
  • Performance increase for FireFox users
  • Less memory on all versions
  • Stability improvements, Hopper keeps on going
  • https support
  • New GUI
  • Better logging
  • Ability to run our Beta Hopper on demand

 

 

UA-19823795-1
You are now being logged in using your Facebook credentials