I'm developing a LAMP online store, which will allow admin to upload multiple images for each item. My concern is - right off the bat there will be 20000 items meaning roughly 60000 images. QUESTIONS: • What is the maximum number of files and/or folders on Linux? • What is the usual way of handling this situation (best practice)? My idea was to make a folder for each item, based on it's unique ID, but then I'd still have 20000 folders in a main uploads folder, and it will grow indefinitely as old items won't be removed. Thanks for any help.

Ext[234] filesystems have a fixed maximum number of inodes; every file or directory requires one inode. You can see the current count and limits with df -i. For example, on a 15GB ext3 filesystem, created with the default settings: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/xvda 19 7% / There's no limit on directories in particular beyond this; keep in mind that every file or directory requires at least one filesystem block (typically 4KB), though, even if it's a directory with only a single item in it. As you can see, though, 80,000 inodes is unlikely to be a problem. And with the dir_index option (enablable with tune2fs), lookups in large directories aren't too much of a big deal. However, note that many administrative tools (such as ls or rm) can have a hard time dealing with directories with too many files in them. As such, it's recommended to split your files up so that you don't have more than a few hundred to a thousand items in any given directory.

An easy way to do this is to hash whatever ID you're using, and use the first few hex digits as intermediate directories. For example, say you have item ID 12345, and it hashes to 'DEADBEEF02842.' You might store your files under /storage/root/d/e/12345. You've now cut the number of files in each directory by 1/256th. If your server's filesystem has the dir_index feature turned on (see tune2fs(8) for details on checking and turning on the feature) then you can reasonably store upwards of 100,000 files in a directory before the performance degrades. ( dir_index has been the default for new filesystems for most of the distributions for several years now, so it would only be an old filesystem that doesn't have the feature on by default.) That said, adding another directory level to reduce the number of files in a directory by a factor of 16 or 256 would drastically improve the chances of things like ls * working without over-running the kernel's maximum argv size. Typically, this is done by something like: /a/a1111 /a/a1112.

I.e., prepending a letter or digit to the path, based on some feature you can compute off the name. (The first two characters of md5sum or sha1sum of the file name is one common approach, but if you have unique object ids, then 'a'+ id% 16 is easy enough mechanism to determine which directory to use.). In addition of the general answers (basically 'don't bother that much', and 'tune your filesystem', and 'organize your directory with subdirectories containing a few thousand files each'): If the individual images are small (e.g. Less than a few kilobytes), instead of putting them in a folder, you could also put them in a database (e.g. With MySQL as a ) or perhaps inside a indexed file. Then each small item won't consume an inode (on many filesystems, each inode wants at least some kilobytes). You could also do that for some threshold (e.g.

Put images bigger than 4kbytes in individual files, and smaller ones in a data base or GDBM file). Of course, don't forget to backup your data (and define a backup stategy).

Foreword by Osamu Tezuka; A Thousand Million Manga. Themes and Readers; Reading, and the Structure of Narrative Comics; Why Japan? A Thousand Years of Manga. The Comic Art Tradition; Western Styles; Safe and Unsafe Art; Comics and the War Machine; The Phoenix Becomes a Godzilla. The Spirit of Japan.

From the PDFtk homepage: PDFtk has a special feature that we added specifically to solve this problem of arranging scanned pages: shuffle. Say you have two PDFs: even.pdf and odd.pdf. Then you can collate them into a single document like this: pdftk A=odd. George Duke The Dream Rarlab. pdf B=even.pdf shuffle A B output collated_pages.pdf If your even pages are in reverse order, you can reverse its page range: pdftk A=odd.pdf B=even.pdf shuffle A Bend-1 output collated_pages.pdf The shuffle feature works by taking one page at a time from each of the input page ranges and assembling them into a new PDF.

You specify these ranges after the shuffle keyword, and you can have more than two ranges. An example of the use of more ranges is: pdftk A=odd.pdf B=even.pdf shuffle A1 B1 A5-6 B2-3 output out. Flash Fxp 3 0 2 Crack Minds. pdf in which case the output contains the first page of A (A1), the first page of B (B1), then the fifth page of A, the second of B, the sixth page of A and finally the third page of B. Of the top of my head, I would combine pdftk with mmv: • First burst both files into separate directories, getting even/001.pdf and odd/001.pdf etc.

• Then use mmv '*.pdf' '#1-a.pdf' on the odd folder, mmv '*.pdf' '#1-b.pdf' on the even folder. • Move everything into one folder. The shell expansion * should now sort odd pages before even pages (001-a, 001-b, 002-a, 002-b etc.). • Use pdftk as in pdftk *.pdf cat output combined.pdf Maybe you have to do the last bit in loops for, say, the first thirty pages, then another thirty pages etc., depending on how robust your shell expansion is with many files.

I was facing the same problem. One file containing the odd, one file containing the even pages of a scanned book. I simply used the built in Windows 7/8/8.1 batch rename capability. 1) Split the pages of each pdf back into seperate files for each page such that one folder contains all odd pages as seperated files and a different folder contains all even pages. 2) Bulk/Batch/Mass rename the files of both folders in the same way. Simply select all files in each folder and rename the first one as a and hit enter.

In doing so, the files in each of the two folders will be numbered as a(1),a(2),a(3). 3) In the folder with the odd pages, copy all files and paste them directly into the same folder. In doing so, it creates copies of the files with the odd pages that will look like a(1) - Copy 4) Move these copied files to the folder containing the even files. This sorts them in front of the even page files (as long as the files are sorted by their names). 5) Merge the the files back into one file by simply following the new naming scheme. In order to merge and split the pdf files I used pdfIll's Pdf Tools which is available for free.