[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] [orion-dev] Orion server scalability roadmap
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Fri, 5 Apr 2013 09:21:57 +0100
- Delivered-to: email@example.com
I posted some information on Virgo/Tomcat scalability to bug 404935. This is a normal Virgo use case.
On 4 Apr 2013, at 20:36, "Mike Milinkovich" <mike.milinkovich@xxxxxxxxxxx> wrote:
> Cross-posting to virgo-dev, in the hopes that perhaps someone there might be
> incented to help out.
>> -----Original Message-----
>> From: orion-dev-bounces@xxxxxxxxxxx [mailto:orion-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of John Arthorne
>> Sent: April-04-13 3:32 PM
>> To: orion-dev@xxxxxxxxxxx
>> Subject: [orion-dev] Orion server scalability roadmap
>> As Orion adoption increases, it has become clear that our initial Orion
>> "demo server" is not up to the task of large scale deployment. As part of
>> Orion 3.0 planning we have been thinking through what it would take to get
>> from our current state to a much more scalable server. What if there were
>> Orion deployments with a million accounts and 100,000 simultaneous users?
>> Where would we fall down, and how. Linked below is an initial assessment
>> our current Orion Java server state, and what it would take to scale up.
>> Note this is not a plan with a specific time goal. The current Orion
>> will likely only be able to tackle a fraction of this work for any given
> four month
>> Orion release. But we want to start from an accurate assessment of the
>> problems and a prioritized roadmap of what work is required. Please read
>> through and provide feedback. What is missing from this list, or how would
>> prioritize differently? Feedback is welcome either on this thread or in
>> following bug report. Ongoing participation in this work is also most
> virgo-dev mailing list