StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POsearching for files from a single folder (knowing prefix) versus searching for files from multiple folders (knowing folder name)
primarykey
Id
2175554
data
AcceptedAnswerId
2175585
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-01T08:57:17.823
FavoriteCount
0
LastActivityDate
2010-02-01T09:05:37.617
LastEditDate
LastEditorUserId
0
OwnerUserId
183760
ParentId
0
PostTypeId
1
Score
0
ViewCount
79
LastEditorDisplayName
text
Body
I've got a system in which users select a couple of options and receive an image based on those options. I'm trying to combine multiple generated images(corresponding to those options) into the requested picture. I'm trying to optimize this so that if, an image exists for a certain option (i.e. the file exists), then there's no need to compute it and we move on to the next step. Should I store these images in different folders, where each folder is an option name? Should I store them in the same folder, adding a prefix corresponding to the option to each image? Should I store the filenames in a database and check there? Which way is faster to check a file for existence? I'm using PHP on Linux, but I'm also interested if the answer varies if I change the programming language or the OS.
Tags
<linux><search><filesystems>
Title
searching for files from a single folder (knowing prefix) versus searching for files from multiple folders (knowing folder name)
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USValentin Brasso
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.