Smalltalk › Gemtalk › GLASS

Multiple Gems on multiple machines with GS WebEdition

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Udo Schneider

Multiple Gems on multiple machines with GS WebEdition

All,

I'm currently considering moving from Magma to GLASS. What's the licensing restriction of the WebEditon?

Can I use multiple Gems on multiple machines to a shared stone? How can I prevent the maching hosting the Stone being the single point of failure? Is this allowed by the WebEdition license?

Thanks,

Udo

Nick

Re: Multiple Gems on multiple machines with GS WebEdition

Hi Udo,

I'm a user of GemStone, so don't consider this an official response.

Theres some good documentation on http://seaside.gemstone.com and links to other sources of information, the best of which is: http://code.google.com/p/glassdb/wiki/TableOfContents

I'm currently considering moving from Magma to GLASS. What's the licensing restriction of the WebEditon?

The link for licencing is: http://seaside.gemstone.com/docs/GLASS-Announcement.htm

Can I use multiple Gems on multiple machines to a shared stone?

The free version doesn't support remote gems.

How can I prevent the maching hosting the Stone being the single point of failure? Is this allowed by the WebEdition license?

I found this response from James Foster to a similar questions in the mail archives:

GemStone/S does not directly support transparent redundancy for the

database. Customers generally use a variety of approaches to address this

issue. First, you can achieve a lot with hardware redundancy (power

supplies, network cards, CPUs, RAM, etc.). Second, you can use SAN disks and

share them across multiple machines. Third, you can keep a backup on another

machine and regularly apply transaction logs from the production machine to

the backup machine. With this approach the backup can be minutes away from

replacing the production machine. None of these are transparent, but they

are what is available.

Hope this helps

Nick

On 23 October 2010 23:00, Udo Schneider <[hidden email]> wrote:

All,

Can I use multiple Gems on multiple machines to a shared stone? How can I prevent the maching hosting the Stone being the single point of failure? Is this allowed by the WebEdition license?

Thanks,

Udo

Udo Schneider

Re: Multiple Gems on multiple machines with GS WebEdition

Hi Nick,

Theres some good documentation on http://seaside.gemstone.com and links to other sources of information, the best of which is: http://code.google.com/p/glassdb/wiki/TableOfContents

Thanks for the pointer - I'm currently relying heavily on this resource while doning a proof-of-concept port.

The link for licencing is: http://seaside.gemstone.com/docs/GLASS-Announcement.htm

RTFM ... it clearly states not Remote Gems for the free versions. What's the licensing metric for the big GS versions? Any hints?

GemStone/S does not directly support transparent redundancy for the
database. Customers generally use a variety of approaches to address this
[...]
are what is available.

Hope this helps

It does help indeed ... although I'm a bit surprised about it ...

As the free version is limited to 2CPUs ... is there any point in running it on a machine with more than 4 cores?

How many requests can be handled by such a machine. Given that 4 cores machines are quite common nowadays I assume that GLASS+httpd will not really use the resources available in terms of RAM and CPU Cores ... or did I get it wrong?

Best Regards,

Udo

Udo Schneider

Re: Multiple Gems on multiple machines with GS WebEdition

All,

The link for licencing is: http://seaside.gemstone.com/docs/GLASS-Announcement.htm
RTFM ... it clearly states not Remote Gems for the free versions. What's the licensing metric for the big GS versions? Any hints?

Just saw that this could be misunderstood (no offense meant) ... the RTFM was meant for me!! (stupid me not reading the docs).

CU,

Udo

Nick

Re: Multiple Gems on multiple machines with GS WebEdition

In reply to this post by Udo Schneider

HI Udo,

It does help indeed ... although I'm a bit surprised about it ...

As the free version is limited to 2CPUs ... is there any point in running it on a machine with more than 4 cores?

How many requests can be handled by such a machine. Given that 4 cores machines are quite common nowadays I assume that GLASS+httpd will not really use the resources available in terms of RAM and CPU Cores ... or did I get it wrong?

Again I speak simply as a user of GemStone - so not an official response. For a lot of a websites using a VPS with some proportion of CPU will be fine. What GemStone are providing in the free offering is highly capable.

Nick

Dale Henrichs

Re: Multiple Gems on multiple machines with GS WebEdition

In reply to this post by Udo Schneider

On 10/25/2010 03:30 AM, Udo Schneider wrote:

> Hi Nick,
>
>> Theres some good documentation on http://seaside.gemstone.com
>> <http://seaside.gemstone.com/> and links to other sources of
>> information, the best of which is:
>> http://code.google.com/p/glassdb/wiki/TableOfContents
> Thanks for the pointer - I'm currently relying heavily on this resource
> while doning a proof-of-concept port.
>
>> The link for licencing is:
>> http://seaside.gemstone.com/docs/GLASS-Announcement.htm
> RTFM ... it clearly states not Remote Gems for the free versions. What's
> the licensing metric for the big GS versions? Any hints?

The basic licensing metric for the non-Web Edition of GemStone/S is
number of CPUs ... under that model you can use any number of machines
and any size db and any size SPC.

I think it is fair to say that the pricing model beyond the Web-Edition
limits is still in flux. At ESUG we announced an increase in the limits
for the Web-Edition and without any special knowledge on my part, I
assume that the pricing will continue to evovle.

>
>> GemStone/S does not directly support transparent redundancy for the
>>
>> database. Customers generally use a variety of approaches to
>> address this
>>
>> [...]
>>
>> are what is available.
>>
>>
>> Hope this helps
> It does help indeed ... although I'm a bit surprised about it ...
>
>
> As the free version is limited to 2CPUs ... is there any point in
> running it on a machine with more than 4 cores?
>

Other processes besides the GemStone processes can take advantage of the
extra cores, so yes there is a point to running on a machine with more
than 2 cores.

> How many requests can be handled by such a machine. Given that 4 cores
> machines are quite common nowadays I assume that GLASS+httpd will not
> really use the resources available in terms of RAM and CPU Cores ... or
> did I get it wrong?

I've run benchmarks against Seaisde2.8 in the past and on a vanilla
linux machine and a 1G SPC, I saw 25 requests per second. When I
switched to using raw I/0 for tranlogs I got up to 50 requests/second.
With Seaside3.0 it is pretty easy to do RESTful processing (no session
state being recorded) and I've run RESTful Seaside2.8 benchmarks that
hit 335 requests/second with 2 cpus. Of course these are just
benchmarks. More details in the following posts:

http://gemstonesoup.wordpress.com/2007/10/19/scaling-seaside-with-gemstones/

http://gemstonesoup.wordpress.com/2008/08/07/making-_k-and-_s-optional-a-seaside-heresy/#benchmark

>
>
> Best Regards,
>
> Udo
>