CMS and scalability of the file system storage identifier

Question

Please note the following:

I store about 1.2 million TIF files ranging in size from 40 KB to 120 KB.

These documents are stored on a Windows server with the NTFS file system.

Documents are stored using the following variables:

•  
• customer
• type of document
• image folder
• actual image

See below:

C:\<client_id>\<doc_type_id>\image001\1.TIF

Example

C:\1\3\image001\1.TiF

This is a PHP hosted system.

Performance is acceptable at this stage. I want to know what the best strategy will do. Given that the number of clients and documents will increase dramatically.

I am considering replacing the full repository with Jackrabbit CMS.

Would that be so? Or

Saves documents in a format, for example:

• Customer
• Document type
• Julian day of the day of the imported document.
• Current user
• 6-

C:\1\1\167\2\453257\image001\image.TIF

?

, CMS vs File-system . , , .

.

Answer 1

. ? , memcached, , , , . jackrabbit , . , . , jackrabbit, , , . 10 000 .

Answer 2

? , , ( , , ...). , , , , , . , - , , - :

c:\<customer_id>\<document_year>\<document_month>\<document_day>\actual_file.tif

, ( ) /.

, - ( ... , ), , " ", , , , ( , ) .

Windows , "" (, c:\documents and settings\university\year1\module21\assignment1.doc), . , , , , - , , , , , - , - , , . .

Answer 3

, , , (SAN/NAS). , , , . , :

NAS1/00/01/86/63/54/89/image01/image.tiff
NAS2/00/02/46/62/22/11/image02/image.tiff
...

gander MogileFS. , , , - - , .

, , , . , , 10.000.