And I can confirm from some recent non-WO experience that database performance can be dramatically improved by being aware of raw disks, partitioninig and clustering image data. Great fun.
geoff
On 12/12/05, Georg Tuparev <[EMAIL PROTECTED]> wrote:
I can confirm Geoff's words in principle. But there is a caveat. If you put more than, say, 2k files in a folder, the file systems slows down. We have a framework that deals with this problem by spreading files in auto-generated folders. Also it is always a good idea to store images (or other BLOBS) in a separate DB (schema) and if the DB supports, use a raw device instead of file system...just my €0.02gtOn Dec 12, 2005, at 9:31 AM, Geoff Hopson wrote:This is exactly how I did the Fortnum & Mason site - they had an extensive product catalog whose images were stored in a database. when the catalog was ready to go live, the images were exported to the file system under the web server. The web app had a runtime switch (mode = deploy) for the 'production' apps which I could use in a WOConditional (set a boolean in Application, then test on application.deploy in the WOConditional. Developers didn't set the switch and therefore would read images from the database.
Worked well.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/geoff.hopson%40gmail.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]
