DirDepth=3 but directories are not created for files...

Previous topic

Setup & design

Next topic

Author	Message
Dariusz Wlodarczyk	Sunday 25 January 2004 5:15:56 pm In the site.ini file we may read: # Directory depth for storing files, this means that it will create # directories out of the first n characters to make sure not too # many files are placed in one directory. For instance a file name # newfile.png will be placed in n/e/w/newfile.png. DirDepth=3 But this not working for me :( I have all files stored i one dir. Maybe I must enable this feature in another place (another setting)? Where ?
Balazs Halasy	Monday 26 January 2004 12:57:53 am If I'm not mistaken, this thing isn't used any more by the image system. The old image system has been replaced with a new one. Which version of eZ publish are you running? B.
Dariusz Wlodarczyk	Monday 26 January 2004 1:53:40 am But this is setting in [FileSettings] not [ImageSettings], so i think this work with uploading binary files, but maybe i'm wrong. Now all uploaded binary files are stored in one dir (var/store/original/application). I have now about 100 files uploaded and speed is ok, but what if i have 100 times more files uploaded ?

Author

Message

Dariusz Wlodarczyk

Sunday 25 January 2004 5:15:56 pm

In the site.ini file we may read:

# Directory depth for storing files, this means that it will create
# directories out of the first n characters to make sure not too
# many files are placed in one directory. For instance a file name
# newfile.png will be placed in n/e/w/newfile.png.
DirDepth=3

But this not working for me :( I have all files stored i one dir. Maybe I must enable this feature in another place (another setting)? Where ?

Balazs Halasy

Monday 26 January 2004 12:57:53 am

If I'm not mistaken, this thing isn't used any more by the image system. The old image system has been replaced with a new one. Which version of eZ publish are you running?

Dariusz Wlodarczyk

Monday 26 January 2004 1:53:40 am

But this is setting in [FileSettings] not [ImageSettings], so i think this work with uploading binary files, but maybe i'm wrong.

Now all uploaded binary files are stored in one dir (var/store/original/application). I have now about 100 files uploaded and speed is ok, but what if i have 100 times more files uploaded ?

eZ debug

Timing:	Jan 31 2025 10:09:35
Script start
Timing:	Jan 31 2025 10:09:35
Module start 'layout'
Timing:	Jan 31 2025 10:09:35
Module start 'content'
Timing:	Jan 31 2025 10:09:35
Module end 'content'
Timing:	Jan 31 2025 10:09:35
Script end

Main resources:

Total runtime	0.0180 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	588.3750	151.2422
Module start 'layout'	0.0056	0.0028	739.6172	36.7109
Module start 'content'	0.0083	0.0083	776.3281	90.1875
Module end 'content'	0.0166	0.0014	866.5156	33.9922
Script end	0.0180		900.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	12.9836	14	0.0002
Check MTime	0.0010	5.7427	14	0.0001
Mysql Total
Database connection	0.0006	3.1036	1	0.0006
Mysqli_queries	0.0035	19.1617	3	0.0012
Looping result	0.0000	0.0768	1	0.0000
Template Total	0.0010	5.6	1	0.0010
Template load	0.0008	4.5462	1	0.0008
Template processing	0.0002	1.0707	1	0.0002
Override
Cache load	0.0006	3.2360	1	0.0006
General
dbfile	0.0034	19.0227	8	0.0004
String conversion	0.0000	0.0543	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs