Thanks.
Any suggestions for extend the file system when the disk I/O issue coming?
how to add more servers and distribute existing files and directories to
them
equally?
"Kevin Spencer" <> 级糶秎ン穝籇: l...
> Hi RedHair,
>
>> Is the FileSystem object of classic ASP only able to work to local file
>> system?
>
> Use the classes in the System.IO namespace. This includes Directory,
> DirectoryInfo, File, FileInfo, and a number of others.
>
>> Btw, even we have a separate centralized file server for file storage
>> only, when
>> the number of directories and files grow up very large, the disk I/O is a
>> issue, how
>> to solve this problem? add new file server and distribute all files to
>> all file servers
>> equally?
>
> Where do you think your database stores data? In the file system.
> Therefore, if you're going to have enough files and folders in the file
> system to slow down the disk I/O, it would have a similar (but worse)
> effect on a SQL Server.
>
> Now, SQL Server uses memory for caching, which cuts down on IO usage. But
> if you were accessing enough files on the disk to cause an IO issue, the
> SQL Server would have either memory issues, due to the caching of these
> image files, or, if the memory is throttled down, IO issues, or both.
>
> So, all things being equal, I would still recommend using the file system.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> Who is Mighty Abbott?
> A twin turret scalawag.
>
> "RedHair" <> wrote in message
> news:...
>> Thanks.
>> Is the FileSystem object of classic ASP only able to work to local file
>> system?
>> Is there any built-in .NET class for ASP.NET to access remote file system
>> directly?
>> or I need to code a customized class and use it via ASP.NET?
>>
>> Btw, even we have a separate centralized file server for file storage
>> only, when
>> the number of directories and files grow up very large, the disk I/O is a
>> issue, how
>> to solve this problem? add new file server and distribute all files to
>> all file servers
>> equally?
>>
>>
>>
>> "Kevin Spencer" <> 级糶秎ン穝籇: bl...
>>>> If store images in file system, is there any limitation of total file
>>>> number
>>>> in a single folder?
>>>
>>> You've got to be kidding. While the answer is, of course, yes, the
>>> number is astronomical. Take a look at your own current file system
>>> under Windows, for example.
>>>
>>>> Btw, if the web site is a web farm, how to store image to a centralized
>>>> file system and retrieve them later?
>>>
>>> In a Web Farm, all the servers are part of the same domain. Therefore,
>>> you can use UNC paths to the files, as long as each machine has
>>> permission to access those folders.
>>>
>>> --
>>> HTH,
>>>
>>> Kevin Spencer
>>> Microsoft MVP
>>> .Net Developer
>>> Who is Mighty Abbott?
>>> A twin turret scalawag.
>>>
>>> "RedHair" <> wrote in message
>>> news:...
>>>> If store images in file system, is there any limitation of total file
>>>> number
>>>> in a single folder?
>>>> Btw, if the web site is a web farm, how to store image to a centralized
>>>> file system and retrieve them later?
>>>>
>>>> Thanks.
>>>>
>>>> "Kevin Spencer" <> 级糶秎ン穝籇:On7sva$ bl...
>>>>> File System. Database is definitely a *lot* harder, not easier, and
>>>>> has a performance hit.
>>>>>
>>>>> Generally, if the images need to be catalogued, you can use a database
>>>>> to store meta-data about the images. Sometimes, however, you can use a
>>>>> folder and/or naming scheme to store the necessary meta-data.
>>>>>
>>>>> --
>>>>> HTH,
>>>>>
>>>>> Kevin Spencer
>>>>> Microsoft MVP
>>>>> .Net Developer
>>>>> Who is Mighty Abbott?
>>>>> A twin turret scalawag.
>>>>>
>>>>> "Adam J Knight" <> wrote in message
>>>>> news:%23HU2kj%...
>>>>>> Hi all,
>>>>>>
>>>>>> Just wondering whats everyones prefered method of storing images ?
>>>>>>
>>>>>> 1) File System
>>>>>> 2) Database (SqlServer) (Seems to be easier, but has a performance
>>>>>> hit)
>>>>>>
>>>>>> Appreciate some insight!!!
>>>>>>
>>>>>> Cheers,
>>>>>> Adam
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Similar Threads
