Loading...

All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Ticket #269 (closed question: wontfix)

Opened 6 years ago

Last modified 6 years ago

Performance using Database File System

Reported by: erik.aandahl@… Owned by: steve@…
Priority: major Component: DatabaseFileSystem
Keywords: Cc:

Description

A few questions about Database File System.
Has the component been tested for performance? Our customer uses one database server for several different web applications. And the site I have in mind will have up to 30.000 files, totalling to about 15GB.
Will disk usage be about the same as when using ordinary file system?
Will the module handle more than one location (both PageFiles and Global)?

Erik Aandahl

Change History

comment:1 Changed 6 years ago by steve@…

The component has been tested for performance and is in use on a site with traffic peaks. I can't reveal the exact numbers, but we ran tests using Load Storm with 10000 concurrent users for 10 minutes. Although the tests did not specifically target the database file system, several of the pages had images from the database file system. The complete database, including content and 3 file systems is about 7GB (backup file size.)

There is per-request-caching implemented for url segments directories and file lookups (as far as I can remember), and file content is cached using the EPiServer Cache Manager (which I now see could be problematic for large files.) See OpenRead in DbFile for more information. A configurable size limit should have been added to avoid caching large files. See #270

I think disk usage will be about the same (content is stored as VarBinary(max)). Depending on the size of the tree, the directory structure will consume some space (but not too much.)

Yes, the system supports several file locations.

Cached or not, you will get more traffic to your database, which you need to plan for.

comment:2 Changed 6 years ago by steve@…

  • Status changed from new to closed
  • Resolution set to wontfix

No need to keep this ticket open any more. Closing it.

Note: See HelpUser/Tickets for help on using tickets.