[Glass] [GS/SS Beta] Scale to multiple nodes sharing a DB?

[James Foster]

On Nov 28, 2013, at 8:31 PM, Mariano Martinez Peck <marianopeck at gmail.com> wrote:

> On Fri, Nov 15, 2013 at 4:34 PM, Martin McClure <martin.mcclure at gemtalksystems.com> wrote:
> On 11/15/2013 09:59 AM, Dale K. Henrichs wrote:
> >
> > Our customers tend to towards larger and larger SPCs and more and more cpus on a single machine for the abosulte fastest performance ... As is always the case the fastest access paths are always memory to memory if you have to go over a wire or hit disk then the performance impact is not transparent ...
> >
> > So in the end, Norbert is correct that there are limitations to what can be achieved by adding multiple machines as opposed to increasing the size of a given machine ... but in the end it does depend upon the characteristics of the application and the size of the working set required ....
> 
> As a counter-example, there are people running successfully with
> hundreds of nodes per stone. Eventually your network becomes the
> bottleneck -- exactly when that happens is very application-specific.
> 
> 
> ok. Just to see if I understand...What they run in each node are gems right? So each node will have 1 SPC and many gems, and all those gems/SPC of all nodes will be talking (wire in the middle) to the one stone in some node?

Yes, each host/machine/node can run Gems that communicate with a central Stone on another host/machine/node. See Figures 3.2 and 3.3 in the System Administration Guide (“Connecting Distributed Systems”).

James

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20131128/095a7697/attachment.html>