Difference between revisions of "Talk:Scalability VAG"

From Second Life Wiki
Jump to navigation Jump to search
Line 53: Line 53:


= Members (Stakeholders) =
= Members (Stakeholders) =
* Welcome, Jesrad. :-)
: FYI the current state of play in this VAG is something like this:
:* We don't know exactly what to analyze for scalability in the new arch until we know how the resources are partitioned into REST services.  Afaik, candidate partitionings haven't been proposed yet either, so this is on hold unless someone wants to kickstart the process with some proposals.  I assume this will happen in the [[REST Services VAG]].
:* Some tools were deemed appropriate for applying actual workloads to the reference implementation of REST services so that we could spot descaling trends early on.  That work is in progress in the [[Multi-Process Client VAG -- draft]], and despite that still being in draft form and in early design state, there is reasonable progress there.  (Feel free to join. :P)
:* I started but did not complete my analysis of mitigating factors that reduce the arithmetic scalability requirement of regions to below that calculated in [[Project_Motivation]].  I must do this.  All help welcome. :P --[[User:Morgaine Dinova|Morgaine Dinova]] 08:40, 12 November 2007 (PST)

Revision as of 09:40, 12 November 2007

Purpose

Areas addressed by this viewpoint

Areas not addressed by this viewpoint

Scalability VAG Glossary

Source of Viewpoint

General concerns addressed by this viewpoint

Dimensions of scalability

Specific concerns within this viewpoint

  • I've purposely placed this section after Dimensions of scalability and not immediately after General concerns addressed by this viewpoint so that the "Dimensions" can act as a first-order template for the specifics.


Use Cases

Proposals and Analysis

Organization

Joining

In world meetings

Meeting Agendas

Chat Logs

Architectural Descriptions/Views used to express this viewpoint

Tools employed by this VAG

External Links

Members (Stakeholders)

  • Welcome, Jesrad. :-)
FYI the current state of play in this VAG is something like this:
  • We don't know exactly what to analyze for scalability in the new arch until we know how the resources are partitioned into REST services. Afaik, candidate partitionings haven't been proposed yet either, so this is on hold unless someone wants to kickstart the process with some proposals. I assume this will happen in the REST Services VAG.
  • Some tools were deemed appropriate for applying actual workloads to the reference implementation of REST services so that we could spot descaling trends early on. That work is in progress in the Multi-Process Client VAG -- draft, and despite that still being in draft form and in early design state, there is reasonable progress there. (Feel free to join. :P)
  • I started but did not complete my analysis of mitigating factors that reduce the arithmetic scalability requirement of regions to below that calculated in Project_Motivation. I must do this. All help welcome. :P --Morgaine Dinova 08:40, 12 November 2007 (PST)