But as I mentioned, storing data in MySQL (or other RDBMSs) would mean I'd have to modify the content types, user folder and stuff. Did you mean the following, for example? 1. A user registers as a member of a CMF site: his member data and credentials all go into MySQL; user folder and member data tool are just wrappers to pool data from MySQL. I wrote a userfolder doing exactly this months ago but realized that the member data schema couldn't be as flexible as a normal member data tool would be as a dynamic dictionary :-( 2. That user starts adding content: internally, binary data such as Images and Files are saved as external files; textual data such as Documents and Artilces go into MySQL, which means Document and Article content types are simple wrappers to pool data from MySQL. Do you suggest these are the only reasonable options I'd have? In fact, I dreaded this since it's a lot more hassle than I wanted to go thru. Plus, I'd still need a dedicated machine for MySQL even if I chose to use ZEO. Running MySQL and ZEO on the same machine seems too much burden on the machine in question (my current MySQL DB machine is a 4-way 2G ram machine and it's already feeling the hit.). Separating them would mean two costly fault-tolerant machines. Too much cost... Well, if you say yes, I'd need to go about taking apart all the content types and tools I've created not to rely 100% on ZODB. Thanks again and I appologize for these constant stupid questions^^ But they're really important to me since I have to shell out the dough soon for new machines anyway, and need a concrete picture of what I'd do with Zope, ZEO and stuff. Best Regards, Wankyu Choi --------------------------------------------------------------- To the dedicated staff at NeoQuest, language is not a problem to be dealt with, but an art waiting to be performed. --------------------------------------------------------------- Wankyou Choi CEO/President NeoQuest Communications, Inc. 3rd Floor, HMC Bldg., 730-14, Yoksam-dong, Kangnam-gu Seoul, Korea Tel: 82-2 - 501 - 7124 Fax: 82-2-501-7058 Corporate Home: http://www.neoqst.com Personal Home: http://www.zoper.net, http://www.neoboard.net e-mail: wankyu@neoqst.com --------------------------------------------------------------- -----Original Message----- From: Andreas Jung [mailto:lists@andreas-jung.com] Sent: Wednesday, January 29, 2003 3:42 PM To: Wankyu Choi; 'Andreas Jung'; zope@zope.org Subject: RE: [Zope] Hardware for Zope + ZEO --On Mittwoch, 29. Januar 2003 15:32 +0900 Wankyu Choi <wankyu@neoqst.com> wrote:
If most Zope users ( including yourself ) feel Filestorage is not a solution for more than 20GB of data, wouldn't ZC feel the same too? It seems the stock Zope is not up to a large-scale web site. (if you call 300,000 user web site large-scale... I wouldn't but...) Some even say a coule of thousand users would be the limit. I've posted similar queries about Zope's scalibility on a number of occasions, but replies suggest "one might do this" kind of stuff. There's been no concrete answer to these queries, an answer out of real experience, not a guesstimation. That confuses me. Does that mean nobody has reached the limit using Zope? 20GB of data is so normal these days. I already have double the amount of data on my site. Guess I'll start worrying about Zope's scalibility again.... Please convince me. Anyone?
The largest Data.fs files I have seen so for and heard of were up to 30-40GB. It is not a question of scalablility but a question of handling. I don't like to handle a single 40GB large file.
One mentioned months ago that Filestorage is so robust that it could withstand most abuse I could throw at it. Okay, I believe it so. But the question still remains. Why couldn't we have a FileStorage that can split over partitions ( in multiple files, I mean, why one single golliath? ) and that has an option to turn off versioning? One might say, "It's opensource, please yourself. Write one yourself." ;-) But I just really wanted to know why ZODB guys hasn't done that. Is there a reason I'm missing? Or is it still on the to-do list?
Maybe I'm assuming wrong. Would you please elaborate what you mean by 'RDBMS backend'? Do you really mean I should write my own products to use MySQL as backend bypassing ZODB , for example? Or is there an RDBMS storage ( Orcale is not an option, if you mean Oracle storage )?
I was not thinking about an RDBMS as storage but about a normal database to store your data. -aj