Georg,
When you say that MySQL does not scale, at what point did you see
performance start to degrade? Was the degradation a function of the
size of the images, size of the database, the number of images, or
number of transactions? I have seen some degradation because of the
application memory requirements to stream out of the database (when
handling images with a filesize greater about 15 Mb), but I don't think
it was because of problems with the database itself. What does
Frontbase do differently?
Thanks,
David
On 12 Dec 2005, at 4:06 PM, Georg Tuparev wrote:
Alex,
Based on my experience in the exact same type of project, I would
strongly discourage you storing images in MySQL. If you decide to use
FrontBase though, it should work fine if you use separate schemas and
raw devices... or possibly without them too. MySQL just does not
scale...
my €0.02
gt
On Dec 12, 2005, at 9:15 PM, Alex Finkel wrote:
The reason is that I am involved in the development of the digital
asset management system, a WO project with the MySQL as a DB. We need
to store the high resolution images (30Mb - 100 Mb), and allow the
users to download them.
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/
programmingosx%40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
