Closed Bug 493979 Opened 15 years ago Closed 15 years ago

Personas uplift / Capacity and performance planning

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: telliott, Assigned: zandr)

References

Details

We're starting to show the seams on the sm-personas box - it's not really equipped for handling a product of this magnitude. The getpersonas.com url still handles the majority of the load, but the underlying problem is fourfold:

1) Disk space: This has been partially alleviated by the mounting of an additional disk, on which I'm logging and doing some archiving. Even so, we're still at 70% on the disk, and it's always going to need monitoring.

2) Performance: The CPU allocation is pushing it, and often hits 100%. Because of the simplicity of the system, external perfomance appears OK for now, but it's going to get worse and there are occasional hiccups.

3) Redundancy: The db is backed up by me doing a periodic copy. Log removal is ad hoc.

4) Capabilities: Many of the dynamic functions we want to do - search, administration, etc - are only possible on this system, and not the static one. This has a twofold effect of slowing development (since some features, such as search, just can't launch) and encouraging traffic to the dynamic box, compounding the other problems.
a complete solution to this shouldn't be a blocker to 1.4. moving this to 1.5 and setting dependencies for 489246 and 493876 (both mapped to 1.5) on this fix.
Target Milestone: -- → 1.5
Blocks: 489246
Blocks: 493876
Should we start looking at transitioning this to a hybrid Labs prod enviro where IT handles scaling app & db ?
Yes. If we get a quick hire for the labs-it guy, this would be a great introductory project for them. If not, you and I can coordinate to put something together.
When you give up on waiting for Labs IT, flip it over to server-ops and we'll take over.
dropping my support in this - would be good to see this uplifted on both the webdev side and ops...
Moving this over to server-ops.  

Since Toby was proactive on this we have some time to plan this.  We'll shoot to touch bases after Toby's back from vacation.
Assignee: telliott → server-ops
Component: Personas → Server Operations
Product: Mozilla Labs → mozilla.org
QA Contact: personas → mrz
Summary: Website: Capacity and performance planning → Personas uplift / Capacity and performance planning
Target Milestone: 1.5 → ---
Version: 0.3 → other
Meant to give this to oremj earlier, clicked the wrong buttons or something.
Assignee: server-ops → oremj
Is there a plan for this written up anywhere?
Plan is not written up. Next step is for mrz, Toby, and Suneel to determine next steps. One of us will write these up and post.
Mostly waiting for Toby to get back, so next week or so.
Assignee: oremj → zandr
Sat down with Zandr today to go over what we need. He'll build us a LAMP stack in production (and will no doubt update this bug as he progresses). We'll then push a copy of the site live to that set of machines.

I think we can bring down personas.services for a couple minutes to move the database over to the new setup. If we punch a hole in the firewall, we can then have personas.services do subsequent reads and writes to the new db, which will prevent any weirdness during the CNAME change. Once we're happy with the new site, we move the getpersonas CNAME over, and redirect personas.services.mozilla.com to getpersonas and we should be all set.

Note that we'll need to change any url references to personas.services, though the redirect will make them work properly anyway.
An update: personas is now working off the new db.

Additionally, we have the site mostly live: http://pm-app-personas01/

The images have only been synched across once - Alexandr is putting a cron to do this regularly. But that should be enough to start testing.

If we open up the beta, I would recommend encouraging users to not upload through the beta site, as that will be a bit of a pain for us to administer (targetted uploads to test things should be fine).
Further update:

Memcache is in place and appears to be working. We'll need to test that carefully.

Stephen has done some basic testing and things look pretty good. Ryan is working on making favorites look good.

Zandr is getting us an external address and setting up the rsync

I think we can release this for beta testing on Monday. Once we do, we should redirect /upload to personas.services so that we keep all the images flowing into one location, but our users can try out the rest of the functionality on the new site.
We are almost ready to launch and were actually live briefly on Weds. evening. We're waiting for an SSL cert for getpersonas.com. (#501845) and plan to launch Monday.
Uplift complete. Share and Enjoy

http://www.getpersonas.com/
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.