L PROTECTED] Cc: "Michael
Andy Bernstein" [EMAIL PROTECTED] Sent: Tuesday, January 16,
Andy 2001 3:22 PM Subject: Re: [Zope-dev] Massive scalability
Michael Bernstein wrote:
So, again: Has anyone run up against any performance or
other limitation
Forwarded to the list to maintain the thread.
Original Message
From: John Eikenberry [EMAIL PROTECTED]
Subject: Re: [Zope-dev] Massive scalability
To: Michael Bernstein [EMAIL PROTECTED]
Michael Bernstein wrote:
John Eikenberry wrote:
Can you tell us a bit about how many
Are you saying that Zope's startup and shutdown time is
affected by the size of the ZODB?
Yep. Over small ZODB's you wont notice the effect until it gets large. I
found it very annoying when doing a lot of work in python and so had two
databases, one with a small amount of data and one with a
D]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 3:43 AM
Subject: Re: [Zope-dev] Massive scalability
Hi Andy,
I'm not sure what you mean by 'interface/way', so.. I'm going to
guess at two possible interpretations.
1) Basically ZPatterns allows you to define classes
On Tuesday 16 January 2001 20:42, Michael Bernstein wrote:
Are you saying that Zope's startup and shutdown time is
affected by the size of the ZODB?
AFAIK on a filestorage zope loads up the indexes (oid, file_offset?) into
memory on start to facilitate object retrieval which impacts start up
y McKay"
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 12:05 PM
Subject: Re: [Zope-dev] Massive scalability
On Tuesday 16 January 2001 20:42, Michael Bernstein wrote:
Are you saying that Zope's startup and shutdown time is
affected by the size of the ZODB?
AFA
While that would work for the simple object case, I find the
prospect of storing a bunch of BLOBs (for the image data of
the Photos) in an RDBMS to be *most* un-appetizing. Storing
them on the server's file-system seems in-elegant as well.
Okey dokey, just a suggestion. I have heard people
Michael Bernstein wrote:
So, again: Has anyone run up against any performance or
other limitations regarding large numbers (hundreds of
thousands or more) of objects stored within the ZODB either
in a BTree Folder or a Rack?
I was looking into the same issues recently, but for a much
ot; [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: "Michael Bernstein" [EMAIL PROTECTED]
Sent: Tuesday, January 16, 2001 3:22 PM
Subject: Re: [Zope-dev] Massive scalability
Michael Bernstein wrote:
So, again: Has anyone run up against any performance or
other limitations regarding lar
John Eikenberry wrote:
Michael Bernstein wrote:
So, again: Has anyone run up against any performance or
other limitations regarding large numbers (hundreds of
thousands or more) of objects stored within the ZODB either
in a BTree Folder or a Rack?
I was looking into the same
Andy McKay wrote:
While that would work for the simple object case, I find the
prospect of storing a bunch of BLOBs (for the image data of
the Photos) in an RDBMS to be *most* un-appetizing. Storing
them on the server's file-system seems in-elegant as well.
Okey dokey, just a
RDM wrote:
On Mon, 15 Jan 2001, Michael Bernstein wrote:
as Squishdot). Adding a dependency on an RDBMS or requiring
additional setup on the server's FS seems a step in the
wrong direction.
[...]
So the question remains: Will either approach (within the
ZODB) allow me to scale the
Andy McKay wrote:
Does ZPatterns provide a nice interface / way for storing classes in a
RDBMS? I have to say using an RDBMS is not as transparent as I would like,
this may may improve it. Finally a reason for me to ZPatterns...
The best way to get a taste is to try it out. The easiest way
Michael Bernstein wrote:
John Eikenberry wrote:
I was looking into the same issues recently, but for a much smaller set of
data (5ish). In my tests ZPatterns/binary-trees scaled well for storage
and retrieval. But ZCatalog did not. It was basically useless for partial
matching
I am currently planning two separate 'Archive' type
projects/Products. In both cases, I need to make sure that
my implementation will scale to hundreds of thousands or
even millions of objects.
I would recommend using an RDMBS behind Zope then. Its faster, simpler and I
have always had
Andy McKay wrote:
I am currently planning two separate 'Archive' type
projects/Products. In both cases, I need to make sure that
my implementation will scale to hundreds of thousands or
even millions of objects.
I would recommend using an RDMBS behind Zope then. Its faster, simpler
I would like to echo Michael's sentiment and comments. I am at the
beginning stage of Zope development of a website which will have
millions of objects of a single object type and multiple of such. I
currently plan on using mounted databases for the various object
repositories and am currently
Jimmie Houchin wrote:
I would like to echo Michael's sentiment and comments. I am at the
beginning stage of Zope development of a website which will have
millions of objects of a single object type and multiple of such.
are your objects intended to be indexed by ZCatalog as well,
or are you
Michael Bernstein wrote:
I am currently planning two separate 'Archive' type
projects/Products. In both cases, I need to make sure that
my implementation will scale to hundreds of thousands or
even millions of objects.
In one project the objects are very simple ZClasses with a
few
Steve Alexander wrote:
Michael Bernstein wrote:
I am currently planning two separate 'Archive' type
projects/Products. In both cases, I need to make sure that
my implementation will scale to hundreds of thousands or
even millions of objects.
In one project the objects are very
20 matches
Mail list logo
