Thanks guys for the help. Steve, the thing is, this is not for one app, but for a container to
hold/manage multiple apps. Think Tomcat or the like. Jeremey reccomends running each
app in its own vm, so that would, I believe, let the system decide how to schedule the apps
and let them each take advantage of one processor which could be ok. I'd lose to some
extent some central management of resources, etc. unless I have a controlling process,
and if one app had significantly greater performance needs I suppose I'd need to spawn a
new copy in another container and figure out how to join state in those two containers.
Basically, trying to figure out in Io, what's the best way to scale with multiple Io webapps.
Maybe by using multiple processors is not the answer ..
--- In iolanguage%40yahoogroups.com">iolanguage
yahoogroups.com, Steve Dekorte <steve
...> wrote:
>
>
> On 25 Dec 2006, at 09:16 pm, neuroboy67 wrote:
> > Let's say one wanted to put together a little container to keep Io
> > coded web apps in memory
> > and get the juicy benefits of that and maybe even run more than one
> > to take advantage of
> > multiple processors but still make sure that things like sessions,
> > or whatever you might
> > imagine are kept in sync.
> >
> > I follow from the discussions here that perhaps the best path to
> > utilize multiple processors
> > and keep objects in sync is to run two(n) VMs and use IPC to
> > harmonize them. Does this still
> > seem true to your big brains?
>
> Yes, but before making your app more complex by using multiple
> processors you might want to make sure it's CPU bound. Otherwise,
> more processors may actually make it slower.
>
> - Steve
>
.